From: "Michael S. Tsirkin" <mst@redhat.com>
To: syzbot <syzbot+cbb68193bdb95af4340a@syzkaller.appspotmail.com>
Cc: 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, parav@nvidia.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_setattr
Date: Sun, 14 May 2023 16:39:36 -0400 [thread overview]
Message-ID: <20230514163907-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <000000000000a9377e05fbac4945@google.com>
On Sun, May 14, 2023 at 12:24:32PM -0700, syzbot wrote:
> 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=16e372c6280000
> start commit: e922ba281a8d Add linux-next specific files for 20230512
> git tree: linux-next
> final oops: https://syzkaller.appspot.com/x/report.txt?x=15e372c6280000
> console output: https://syzkaller.appspot.com/x/log.txt?x=11e372c6280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=17a4c2d44484b62f
> dashboard link: https://syzkaller.appspot.com/bug?extid=cbb68193bdb95af4340a
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=172a21c6280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b67fc6280000
>
> Reported-by: syzbot+cbb68193bdb95af4340a@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
I don't see how this can be related, I don't think the test setup uses
vdpa sim at all.
--
MST
next prev parent reply other threads:[~2023-05-14 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000a74de505f2349eb1@google.com>
2023-05-14 19:24 ` [syzbot] [ext4?] possible deadlock in ext4_setattr syzbot
2023-05-14 20:39 ` Michael S. Tsirkin [this message]
2023-05-15 0:53 ` Theodore Ts'o
2023-05-15 1:15 ` Theodore Ts'o
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=20230514163907-mutt-send-email-mst@kernel.org \
--to=mst@redhat.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=parav@nvidia.com \
--cc=syzbot+cbb68193bdb95af4340a@syzkaller.appspotmail.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 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).