All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2e6495950edcf7fbfccf@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_page_mkwrite
Date: Sun, 17 Nov 2024 09:49:02 -0800	[thread overview]
Message-ID: <673a2c8e.050a0220.87769.0012.GAE@google.com> (raw)
In-Reply-To: <00000000000093a1ca0621e8d336@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=10fff130580000
start commit:   b5a24181e461 Merge tag 'trace-ringbuffer-v6.12-rc7-2' of g..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=12fff130580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14fff130580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1503500c6f615d24
dashboard link: https://syzkaller.appspot.com/bug?extid=2e6495950edcf7fbfccf
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17f252e8580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12ecd2c0580000

Reported-by: syzbot+2e6495950edcf7fbfccf@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

  parent reply	other threads:[~2024-11-17 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  9:35 [syzbot] [ocfs2?] possible deadlock in ocfs2_page_mkwrite syzbot
2024-11-17  1:25 ` syzbot
2024-11-17 17:49 ` syzbot [this message]
2025-10-23  2:48 ` 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=673a2c8e.050a0220.87769.0012.GAE@google.com \
    --to=syzbot+2e6495950edcf7fbfccf@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.