On 11.09.19 г. 10:54 ч., Zdenek Sojka wrote: > Hello, > > this is my fourth attempt to post this message to the mailing list; this time, without any attached kernel config (because it has over 100KiB). I also tried contacting the kernel btrfs maintainers directly by email, but they probably also didn't receive the message... > > I am running kernel with lock debugging enabled since I am quite often encountering various lockups and hung tasks. Several of the problems have been fixed recently, but not all; I don't know if the following backtrace is related to the hangups, or if it is just a false positive. > > $ uname -a > Linux zso 5.2.11-gentoo #2 SMP Fri Aug 30 07:18:03 CEST 2019 x86_64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz GenuineIntel GNU/Linux > > The kernel has a distro patchset applied (which should not affect this, but you can never say that for sure) and I am compiling at -O3 -fipa-pta -march=native instead of default -O2 (gcc-8.3.0). > > Please let me know if I can provide any more information. > > Best regards, > Zdenek Sojka > > The dmesg warning I recently triggered: This already received a patch in [PATCH] btrfs: nofs inode allocations It's just not reviewed/merged yet. Care to test that patch if you can reliably reproduce this? <snip>
