From: syzbot <syzbot+298c5d8fb4a128bc27b0@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, elic@nvidia.com, jasowang@redhat.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mst@redhat.com, parav@nvidia.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_xattr_inode_iget
Date: Mon, 08 May 2023 03:39:29 -0700 [thread overview]
Message-ID: <000000000000ec231605fb2c4056@google.com> (raw)
In-Reply-To: <0000000000005937d105f24c9809@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=1094ee22280000
start commit: 83e5775d7afd Add linux-next specific files for 20230505
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1294ee22280000
console output: https://syzkaller.appspot.com/x/log.txt?x=1494ee22280000
kernel config: https://syzkaller.appspot.com/x/.config?x=d0c6b4b7069d73cf
dashboard link: https://syzkaller.appspot.com/bug?extid=298c5d8fb4a128bc27b0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17b7c75c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1284b832280000
Reported-by: syzbot+298c5d8fb4a128bc27b0@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
prev parent reply other threads:[~2023-05-08 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:27 [syzbot] [ext4?] possible deadlock in ext4_xattr_inode_iget syzbot
2023-05-08 3:21 ` syzbot
2023-05-08 10:39 ` syzbot [this message]
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=000000000000ec231605fb2c4056@google.com \
--to=syzbot+298c5d8fb4a128bc27b0@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.