On (11/30/17 09:16), Dmitry Vyukov wrote:
> to be honest, this backtrace hardly makes any sense to me.
> I need some help here.
You can try dirty patch from here:
It should make KASAN print the exact variable name and frame where it
would be good if Fengguang can try this out. I can't reproduce the
problem on my x86 box (linux-next and Linus's trees both work fine
for me with KASAN + lockdep + TRACE_IRQ).