All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4b12286339fe4c2700c1@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@lst.de, jack@suse.com,
	 jfs-discussion@lists.sourceforge.net,
	linux-block@vger.kernel.org,  linux-kernel@vger.kernel.org,
	ming.lei@redhat.com, shaggy@kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] INFO: task hung in __bread_gfp (7)
Date: Sun, 21 Sep 2025 06:31:03 -0700	[thread overview]
Message-ID: <68cffe17.050a0220.13cd81.0036.GAE@google.com> (raw)
In-Reply-To: <68ce15c0.050a0220.13cd81.000e.GAE@google.com>

syzbot has bisected this issue to:

commit f1be1788a32e8fa63416ad4518bbd1a85a825c9d
Author: Ming Lei <ming.lei@redhat.com>
Date:   Fri Oct 25 00:37:20 2024 +0000

    block: model freeze & enter queue as lock for supporting lockdep

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=113248e2580000
start commit:   097a6c336d00 Merge tag 'trace-rv-v6.17-rc5' of git://git.k..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=133248e2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=153248e2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4d8792ecb6308d0f
dashboard link: https://syzkaller.appspot.com/bug?extid=4b12286339fe4c2700c1
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=116310e2580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1430b0e2580000

Reported-by: syzbot+4b12286339fe4c2700c1@syzkaller.appspotmail.com
Fixes: f1be1788a32e ("block: model freeze & enter queue as lock for supporting lockdep")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      reply	other threads:[~2025-09-21 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20  2:47 [syzbot] [jfs?] INFO: task hung in __bread_gfp (7) syzbot
2025-09-21 13:31 ` 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=68cffe17.050a0220.13cd81.0036.GAE@google.com \
    --to=syzbot+4b12286339fe4c2700c1@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jack@suse.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=shaggy@kernel.org \
    --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.