Qu Wenruo writes:
On 2020/7/16 上午8:40, Chris Down wrote:
Qu Wenruo writes:
Would you please provide the full call trace (especially the address
causing the NULL pointer deref) and the reproducer (if possible)?
I'll try to reproduce it again when I have time. I didn't have kdump
set, and am not currently running linux-next, so until then, you can
have this crappy photo that I rushed to take earlier before panic=30
took effect :-)
The linux-next is using an older version of that patch, which has a bad
memory allocation inside atomic critical section.
If you're unlucky enough, it could cause various weird bugs.
Thankfully, David has exposed it and the latest version in btrfs tree
should have it fixed.
Great, thanks! When I run my tests again on linux-next I'll be sure to reapply
the latest version of your patch first, then.
Thanks,
Chris
