From: syzbot <syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com>
To: chao@kernel.org, hdanton@sina.com, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry
Date: Thu, 24 Aug 2023 08:55:33 -0700 [thread overview]
Message-ID: <0000000000001b658e0603ad424d@google.com> (raw)
In-Reply-To: <0000000000000f188605ffdd9cf8@google.com>
syzbot has bisected this issue to:
commit 5eda1ad1aaffdfebdecf7a164e586060a210f74f
Author: Jaegeuk Kim <jaegeuk@kernel.org>
Date: Wed Jun 28 08:00:56 2023 +0000
f2fs: fix deadlock in i_xattr_sem and inode page lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=167691b7a80000
start commit: cacc6e22932f tpm: Add a helper for checking hwrng enabled
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=157691b7a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=117691b7a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=171b698bc2e613cf
dashboard link: https://syzkaller.appspot.com/bug?extid=a4976ce949df66b1ddf1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103c6bb3a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17bb51c7a80000
Reported-by: syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com
Fixes: 5eda1ad1aaff ("f2fs: fix deadlock in i_xattr_sem and inode page lock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-24 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 3:55 [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-08-24 15:55 ` syzbot [this message]
2023-08-25 1:08 ` Chao Yu
2023-08-25 1:47 ` syzbot
2023-08-25 5:37 ` [PATCH] f2fs: fix deadlock in f2f2_add_dentry Lizhi Xu
2023-09-06 12:56 ` Tetsuo Handa
2023-10-26 6:59 ` [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-10-26 9:21 ` Aleksandr Nogikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000001b658e0603ad424d@google.com \
--to=syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).