Linus Torvalds writes: (Summary) Ugh, that lustre code is disgusting.
Ugh, that lustre code is disgusting.
I thought we were getting rid of it.
I thought we were getting rid of it.
Anyway, I started looking at why the stack trace is such an incredible mess, with lots of stale entries.
mess, with lots of stale entries.
The reason (well, _one_ reason) seems to be "ksocknal_startup". I'm getting the feeling that KASAN is making things worse because probably it's disabling all the sane stack frame stuff (ie no merging of stack slot entries, perhaps?).
of stack slot entries, perhaps?).
Without KASAN (but also without a lot of other things, so I might be blaming KASAN incorrectly), the stack usage of ksocknal_startup() is just under 100 bytes, so if it is KASAN, it's really a big difference.
Ugh, that lustre code is disgusting.
I thought we were getting rid of it.
I thought we were getting rid of it.
Anyway, I started looking at why the stack trace is such an incredible mess, with lots of stale entries.
mess, with lots of stale entries.
The reason (well, _one_ reason) seems to be "ksocknal_startup". I'm getting the feeling that KASAN is making things worse because probably it's disabling all the sane stack frame stuff (ie no merging of stack slot entries, perhaps?).
of stack slot entries, perhaps?).
Without KASAN (but also without a lot of other things, so I might be blaming KASAN incorrectly), the stack usage of ksocknal_startup() is just under 100 bytes, so if it is KASAN, it's really a big difference.