From: "Michael S. Tsirkin" <mst@redhat.com>
To: syzbot <syzbot+843fa26882088a9ee7e3@syzkaller.appspotmail.com>
Cc: elic@nvidia.com, jasowang@redhat.com, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
mark@fasheh.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_reserve_local_alloc_bits
Date: Sun, 15 Sep 2024 06:18:43 -0400 [thread overview]
Message-ID: <20240915061811-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0000000000000c5506062224dd83@google.com>
On Sun, Sep 15, 2024 at 02:13:02AM -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=174bbc77980000
> start commit: 0babf683783d Merge tag 'pinctrl-v6.11-4' of git://git.kern..
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=14cbbc77980000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10cbbc77980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=1c9e296880039df9
> dashboard link: https://syzkaller.appspot.com/bug?extid=843fa26882088a9ee7e3
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=129a6407980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167617c7980000
>
> Reported-by: syzbot+843fa26882088a9ee7e3@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
something very weird going on here.
don't see how this can thinkably cause a deadlock in ocfs.
prev parent reply other threads:[~2024-09-15 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 12:35 [syzbot] [ocfs2?] possible deadlock in ocfs2_reserve_local_alloc_bits syzbot
2024-09-13 12:03 ` syzbot
2024-09-15 9:13 ` syzbot
2024-09-15 10:18 ` Michael S. Tsirkin [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=20240915061811-mutt-send-email-mst@kernel.org \
--to=mst@redhat.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=ocfs2-devel@lists.linux.dev \
--cc=ocfs2-devel@oss.oracle.com \
--cc=parav@nvidia.com \
--cc=syzbot+843fa26882088a9ee7e3@syzkaller.appspotmail.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.