[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240730144858.GJ17473@twin.jikos.cz>
Date: Tue, 30 Jul 2024 16:48:58 +0200
From: David Sterba <dsterba@...e.cz>
To: syzbot <syzbot+2f3cc5860d147a83eb3d@...kaller.appspotmail.com>
Cc: clm@...com, dsterba@...e.com, josef@...icpanda.com,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in btrfs_free_fs_info
On Wed, May 29, 2024 at 08:24:32AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 56fb6f92854f Merge tag 'drm-next-2024-05-25' of https://gi..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15874672980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2b8d1faad9ceb620
> dashboard link: https://syzkaller.appspot.com/bug?extid=2f3cc5860d147a83eb3d
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: i386
>
> Unfortunately, I don't have any reproducer for this issue yet.
Most likely this was a side effect of bug fixed by commit f3a5367c679d
("btrfs: protect folio::private when attaching extent buffer folios").
There are only two syzbot report and the timeframe corresponds with
increased number of bogus errors caused by use-after-free of a page.
The fix is best guess.
#syz fix: btrfs: protect folio::private when attaching extent buffer folios
> assertion failed: percpu_counter_sum_positive(em_counter) == 0, in fs/btrfs/disk-io.c:1274
Could be a valid bug, eg. some structures leaked but the circumstances
point more towards the page reuse.
Powered by blists - more mailing lists