From: syzbot <syzbot+ca440b457d21568f8021@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_fiemap
Date: Fri, 11 Oct 2024 13:59:02 -0700 [thread overview]
Message-ID: <67099196.050a0220.4cbc0.0017.GAE@google.com> (raw)
In-Reply-To: <000000000000cb688206213d1bda@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=13a0a840580000
start commit: 1d227fcc7222 Merge tag 'net-6.12-rc3' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1060a840580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17a0a840580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7a3fccdd0bb995
dashboard link: https://syzkaller.appspot.com/bug?extid=ca440b457d21568f8021
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142fc840580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15026b27980000
Reported-by: syzbot+ca440b457d21568f8021@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-10-11 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 20:43 [syzbot] [ocfs2?] possible deadlock in ocfs2_fiemap syzbot
2024-09-29 7:52 ` syzbot
2024-10-17 8:55 ` [PATCH] ocfs2: Fix " Lizhi Xu
2024-10-11 20:59 ` syzbot [this message]
2024-10-17 1:52 ` [syzbot] Re: [syzbot] [ocfs2?] " syzbot
2024-10-17 3:19 ` syzbot
2025-10-23 8:33 ` syzbot
[not found] <20241017015210.3665821-1-lizhi.xu@windriver.com>
2024-10-17 2:18 ` syzbot
[not found] <20241017031934.156050-1-lizhi.xu@windriver.com>
2024-10-17 3:51 ` 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=67099196.050a0220.4cbc0.0017.GAE@google.com \
--to=syzbot+ca440b457d21568f8021@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 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.