From: syzbot <syzbot+e0055ea09f1f5e6fabdd@syzkaller.appspotmail.com>
To: elic@nvidia.com, jasowang@redhat.com, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
mark@fasheh.com, mst@redhat.com, ocfs2-devel@lists.linux.dev,
ocfs2-devel@oss.oracle.com, parav@nvidia.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_get_system_file_inode
Date: Sat, 14 Sep 2024 00:53:02 -0700 [thread overview]
Message-ID: <66e540de.050a0220.175489.0002.GAE@google.com> (raw)
In-Reply-To: <000000000000e28810061fb68dd0@google.com>
syzbot has bisected this issue to:
commit a3c06ae158dd6fa8336157c31d9234689d068d02
Author: Parav Pandit <parav@nvidia.com>
Date: Tue Jan 5 10:32:03 2021 +0000
vdpa_sim_net: Add support for user supported devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17ea8407980000
start commit: 196145c606d0 Merge tag 'clk-fixes-for-linus' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=141a8407980000
console output: https://syzkaller.appspot.com/x/log.txt?x=101a8407980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1c9e296880039df9
dashboard link: https://syzkaller.appspot.com/bug?extid=e0055ea09f1f5e6fabdd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16fdd49f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f5a7c7980000
Reported-by: syzbot+e0055ea09f1f5e6fabdd@syzkaller.appspotmail.com
Fixes: a3c06ae158dd ("vdpa_sim_net: Add support for user supported devices")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-09-14 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 10:46 [syzbot] [ocfs2?] possible deadlock in ocfs2_get_system_file_inode syzbot
2024-09-14 7:53 ` syzbot [this message]
2024-09-19 14:24 ` [syzbot] " syzbot
2024-09-23 11:26 ` syzbot
2024-09-24 9:04 ` syzbot
[not found] <CAABpPxQ-H8MjYrG3VUdR-rUFDrnVwJ5aFJaXFGJ2GpJYWD65pQ@mail.gmail.com>
2024-09-19 20:35 ` [syzbot] [ocfs2?] " syzbot
[not found] <CAABpPxQg+RmC_7udiOmj49MuP3E1B+6bbQQiyTrzzEz0Qei1QA@mail.gmail.com>
2024-09-23 12:18 ` syzbot
[not found] <CAABpPxTRUTjc_S-i_Z+o9fDzi4JtGiKN2VeaXQngeioqh3d+zA@mail.gmail.com>
2024-09-24 9:25 ` 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=66e540de.050a0220.175489.0002.GAE@google.com \
--to=syzbot+e0055ea09f1f5e6fabdd@syzkaller.appspotmail.com \
--cc=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=mst@redhat.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=ocfs2-devel@oss.oracle.com \
--cc=parav@nvidia.com \
--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