linux-kernel - Re: [btrfs] 62bd8124e2: WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 16 Jun 2022 10:42:04 +0800
From:   Oliver Sang <oliver.sang@...el.com>
To:     Filipe Manana <fdmanana@...nel.org>
Cc:     0day robot <lkp@...el.com>, LKML <linux-kernel@...r.kernel.org>,
        linux-btrfs <linux-btrfs@...r.kernel.org>, lkp@...ts.01.org
Subject: Re: [btrfs] 62bd8124e2:
 WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block_rsv[btrfs]

hi, Filipe Manana,

On Mon, Jun 13, 2022 at 11:50:05AM +0100, Filipe Manana wrote:
> 
> Thanks for running the test again Oliver.
> Running the fxmark test on my machines, I can't trigger anything.
> 
> May I ask you to run again the test but with the attached debug patch
> on top of it?

I reran the test by applied your patch upon 62bd8124e2. one dmesg is attached.

not sure if it supplies enough information? we need some extra effort to
enable below ftrace in our auto-test framework. so if dmesg is good enough,
please let us know, then we can save some efforts :) Thanks a lot!

> 
> Also, if possible, with ftrace enabled like this:
> 
> modprobe btrfs
> echo 0 > /sys/kernel/debug/tracing/tracing_on
> echo > /sys/kernel/debug/tracing/trace
> echo $((1 << 24)) > /sys/kernel/debug/tracing/buffer_size_kb
> echo nop > /sys/kernel/debug/tracing/current_tracer
> echo 1 > /sys/kernel/tracing/events/btrfs/btrfs_space_reservation/enable
> 
> echo 1 > /sys/kernel/debug/tracing/tracing_on
> 
> <run the test>
> 
> echo 0 > /sys/kernel/debug/tracing/tracing_on
> 
> Then collect the trace to a file and send it over to me:
> 
> cat /sys/kernel/debug/tracing/trace | xz -9 > trace.txt.xz
> 
> And of course, the dmesg result as well.
> 
> Thanks!
> 
> 
> 
> >
> > >


Download attachment "dmesg.xz" of type "application/x-xz" (115420 bytes)