From: syzbot <syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com>
To: chao@kernel.org, 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: [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_getxattr
Date: Fri, 14 Jul 2023 08:11:31 -0700 [thread overview]
Message-ID: <00000000000029c576060073dd62@google.com> (raw)
In-Reply-To: <0000000000005921ef05ffddc3b7@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=1177322aa80000
start commit: 3f01e9fed845 Merge tag 'linux-watchdog-6.5-rc2' of git://w..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1377322aa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1577322aa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=29fd3392a08741ef
dashboard link: https://syzkaller.appspot.com/bug?extid=e5600587fa9cbf8e3826
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1336f364a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=130a365aa80000
Reported-by: syzbot+e5600587fa9cbf8e3826@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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com>
To: chao@kernel.org, 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_getxattr
Date: Fri, 14 Jul 2023 08:11:31 -0700 [thread overview]
Message-ID: <00000000000029c576060073dd62@google.com> (raw)
In-Reply-To: <0000000000005921ef05ffddc3b7@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=1177322aa80000
start commit: 3f01e9fed845 Merge tag 'linux-watchdog-6.5-rc2' of git://w..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1377322aa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1577322aa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=29fd3392a08741ef
dashboard link: https://syzkaller.appspot.com/bug?extid=e5600587fa9cbf8e3826
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1336f364a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=130a365aa80000
Reported-by: syzbot+e5600587fa9cbf8e3826@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-07-14 15:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 4:06 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_getxattr syzbot
2023-07-07 4:06 ` syzbot
2023-07-10 4:13 ` [f2fs-dev] " syzbot
2023-07-10 4:13 ` syzbot
2023-07-14 15:11 ` syzbot [this message]
2023-07-14 15:11 ` syzbot
2023-08-18 19:51 ` [f2fs-dev] " Jaegeuk Kim
2023-08-18 19:51 ` Jaegeuk Kim
2023-08-18 19:51 ` [f2fs-dev] " syzbot
2023-08-18 19:51 ` syzbot
2023-08-18 20:15 ` [f2fs-dev] " Jaegeuk Kim
2023-08-18 20:15 ` Jaegeuk Kim
2023-08-18 21:02 ` [f2fs-dev] " syzbot
2023-08-18 21:02 ` syzbot
2023-08-18 21:15 ` [f2fs-dev] " Jaegeuk Kim
2023-08-18 21:15 ` Jaegeuk Kim
2023-08-18 21:49 ` [f2fs-dev] " syzbot
2023-08-18 21:49 ` syzbot
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=00000000000029c576060073dd62@google.com \
--to=syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.