[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240730141656.GD17473@twin.jikos.cz>
Date: Tue, 30 Jul 2024 16:16:56 +0200
From: David Sterba <dsterba@...e.cz>
To: syzbot <syzbot+8e86db7d430e87415248@...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?] INFO: trying to register non-static key in
btrfs_stop_all_workers
On Fri, Jun 07, 2024 at 09:19:28PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: f06ce441457d Merge tag 'loongarch-fixes-6.10-1' of git://g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=176b7026980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=998c63c06e77f5e7
> dashboard link: https://syzkaller.appspot.com/bug?extid=8e86db7d430e87415248
> 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's only one 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
Powered by blists - more mailing lists