[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241107171441.he2rix37qopi6ane@quack3>
Date: Thu, 7 Nov 2024 18:14:41 +0100
From: Jan Kara <jack@...e.cz>
To: syzbot <syzbot+ee72b9a7aad1e5a77c5c@...kaller.appspotmail.com>
Cc: adilger.kernel@...ger.ca, adilger@...ger.ca, eadavis@...com,
hdanton@...a.com, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com, tytso@....edu,
wojciech.gladysz@...ogain.com
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_xattr_inode_iget (3)
On Sat 02-11-24 15:58:03, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit d1bc560e9a9c78d0b2314692847fc8661e0aeb99
> Author: Wojciech Gładysz <wojciech.gladysz@...ogain.com>
> Date: Thu Aug 1 14:38:27 2024 +0000
>
> ext4: nested locking for xattr inode
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1245f55f980000
> start commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=1a07d5da4eb21586
> dashboard link: https://syzkaller.appspot.com/bug?extid=ee72b9a7aad1e5a77c5c
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12407f45180000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=140d9db1180000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
Makes sense:
#syz fix: ext4: nested locking for xattr inode
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists