[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240222100143.ibz76z7uapncfo4x@quack3>
Date: Thu, 22 Feb 2024 11:01:43 +0100
From: Jan Kara <jack@...e.cz>
To: syzbot <syzbot+41a88b825a315aac2254@...kaller.appspotmail.com>
Cc: akpm@...ux-foundation.org, axboe@...nel.dk, brauner@...nel.org,
eadavis@...com, ernesto.mnd.fernandez@...il.com, jack@...e.cz,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
slava@...eyko.com, syzkaller-bugs@...glegroups.com,
torvalds@...ux-foundation.org, willy@...radead.org
Subject: Re: [syzbot] [hfs?] possible deadlock in hfs_extend_file (2)
On Wed 21-02-24 20:10:04, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@...e.cz>
> Date: Wed Nov 1 17:43:10 2023 +0000
>
> fs: Block writes to mounted block devices
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12bedb0c180000
> start commit: 610a9b8f49fb Linux 6.7-rc8
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=247b5a935d307ee5
> dashboard link: https://syzkaller.appspot.com/bug?extid=41a88b825a315aac2254
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1552fe19e80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1419bcade80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs: Block writes to mounted block devices
Unlikely. The report seems more like a lockdep annotation problem where
different btrees used in HFS share the same lockdep key.
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists