From: syzbot <syzbot+9dd7dbb1a4b915dee638@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.lei@redhat.com,
nilay@linux.ibm.com, syzkaller-bugs@googlegroups.com,
thomas.hellstrom@linux.intel.com, yanjun.zhu@linux.dev
Subject: Re: [syzbot] [block?] possible deadlock in blk_mq_freeze_queue_nomemsave
Date: Thu, 03 Apr 2025 22:40:04 -0700 [thread overview]
Message-ID: <67ef70b4.050a0220.9040b.0334.GAE@google.com> (raw)
In-Reply-To: <67ea99e0.050a0220.3c3d88.0042.GAE@google.com>
syzbot has bisected this issue to:
commit ffa1e7ada456087c2402b37cd6b2863ced29aff0
Author: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Date: Tue Mar 18 09:55:48 2025 +0000
block: Make request_queue lockdep splats show up earlier
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=172e2fb0580000
start commit: 92b71befc349 Merge tag 'objtool-urgent-2025-04-01' of git:..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14ae2fb0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae2fb0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=47cc4b0c03278250
dashboard link: https://syzkaller.appspot.com/bug?extid=9dd7dbb1a4b915dee638
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1680d998580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1180d998580000
Reported-by: syzbot+9dd7dbb1a4b915dee638@syzkaller.appspotmail.com
Fixes: ffa1e7ada456 ("block: Make request_queue lockdep splats show up earlier")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-04-04 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 13:34 [syzbot] [block?] possible deadlock in blk_mq_freeze_queue_nomemsave syzbot
2025-04-03 8:34 ` syzbot
2025-04-04 13:50 ` Ming Lei
2025-04-04 15:01 ` syzbot
2025-04-04 5:40 ` syzbot [this message]
[not found] <20250404100710.3803-1-hdanton@sina.com>
2025-04-04 15:14 ` 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=67ef70b4.050a0220.9040b.0334.GAE@google.com \
--to=syzbot+9dd7dbb1a4b915dee638@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=yanjun.zhu@linux.dev \
/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.