All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+867b0179d31db9955876@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	 mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
	ming.lei@redhat.com,  rostedt@goodmis.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] possible deadlock in loop_reconfigure_limits
Date: Sat, 16 Nov 2024 15:33:01 -0800	[thread overview]
Message-ID: <67392bad.050a0220.e1c64.0009.GAE@google.com> (raw)
In-Reply-To: <67336557.050a0220.a0661.041e.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=129b52c0580000
start commit:   929beafbe7ac Add linux-next specific files for 20241108
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=119b52c0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=169b52c0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=75175323f2078363
dashboard link: https://syzkaller.appspot.com/bug?extid=867b0179d31db9955876
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11b520c0580000

Reported-by: syzbot+867b0179d31db9955876@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

  parent reply	other threads:[~2024-11-16 23:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 14:25 [syzbot] [block?] possible deadlock in loop_reconfigure_limits syzbot
2024-11-13  9:14 ` Ming Lei
2024-11-13  9:25   ` syzbot
2024-11-13  9:41 ` Ming Lei
2024-11-13  9:55   ` syzbot
2024-11-16 23:33 ` syzbot [this message]
2024-11-30 23:14 ` Hillf Danton
2024-12-01  0:11   ` 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=67392bad.050a0220.e1c64.0009.GAE@google.com \
    --to=syzbot+867b0179d31db9955876@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=rostedt@goodmis.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.