On Sun, Oct 29, 2017 at 4:48 PM, Fengguang Wu <fengguang.wu@xxxxxxxxx> wrote:
Here are 3 dmesgs related to wireless and 1 from ethernet.
Fengguang, these would be lovelier still _if_ you have DEBUG_INFO
enabled on the kernel, and your script were to find things like
"symbol+0xhex/0xhex", and run "./scripts/faddr2line" on them.
So
[ 235.425464] BUG: unable to handle kernel paging request at 0000000000010007
[ 235.425470] IP: run_timer_softirq+0x13a/0x470
would also then have
run_timer_softirq at timer.c:XYZ
which would make it easier to see exactly _what_ it is that faults. As
it is, I think there's a fair number of inlining that makes it hard to
see the cause, but that faddrtoline would make very obvious.
Finding that "symbol+xyz/abc" pattern should be fairly easy to
automate, and should fit the 0day model fairly well. No?