[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000000000044b90e061326b102@google.com>
Date: Fri, 08 Mar 2024 06:06:04 -0800
From: syzbot <syzbot+352d78bd60c8e9d6ecdc@...kaller.appspotmail.com>
To: adilger.kernel@...ger.ca, axboe@...nel.dk, brauner@...nel.org,
elic@...dia.com, jack@...e.cz, jasowang@...hat.com,
linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev, mst@...hat.com,
nathan@...nel.org, ndesaulniers@...gle.com, parav@...dia.com,
syzkaller-bugs@...glegroups.com, trix@...hat.com, tytso@....edu
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_xattr_inode_iget (2)
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=14f08e0a180000
start commit: 610a9b8f49fb Linux 6.7-rc8
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=56c2c781bb4ee18
dashboard link: https://syzkaller.appspot.com/bug?extid=352d78bd60c8e9d6ecdc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a4d65ee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1715ad7ee80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Block writes to mounted block devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Powered by blists - more mailing lists