Re:Hunting a Linux kernel bug
by rvz on Wednesday April 29, 2020 @08:09AM
(#23018155)
Very good in-depth analysis and low-level bug hunting. It's always interesting to see blogposts that give an insight into a bug found in a userland application only to start digging into the internals of the Linux Kernel. The technical background in this post really does help setting up the whole context into understanding the data structures and concepts involved in fixing this bug.
> There are a number of places where the packet could be dropped, too many to inspect every possible line of Linux kernel code. To find the offending code, we turned on all routing trace points via /sys/kernel/debug/tracing/events/fib/enable.
I wonder if that this is one of many trace points one could use but for another particular component or subsystem in the kernel, if that makes sense? That would be very interesting to know.
It's also great to see that it's upstreamed as an actual contribution as also linked in the article. [0]
> There are a number of places where the packet could be dropped, too many to inspect every possible line of Linux kernel code. To find the offending code, we turned on all routing trace points via /sys/kernel/debug/tracing/events/fib/enable.
I wonder if that this is one of many trace points one could use but for another particular component or subsystem in the kernel, if that makes sense? That would be very interesting to know.
It's also great to see that it's upstreamed as an actual contribution as also linked in the article. [0]
Impressive!
[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...