All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+fefa0af09f7891b1800e@syzkaller.appspotmail.com>
To: eadavis@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] general protection fault in blk_mq_quiesce_queue
Date: Fri, 04 Sep 2026 02:33:02 -0700	[thread overview]
Message-ID: <6a9a904e.9266084e.bf0d7.060f.GAE@google.com> (raw)
In-Reply-To: <20260904091018.606487-1-eadavis@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in nvme_loop_reset_ctrl_work

------------[ cut here ]------------
1
WARNING: drivers/nvme/target/loop.c:457 at nvme_loop_reset_ctrl_work+0x1d4/0x620 drivers/nvme/target/loop.c:457, CPU#3: kworker/u33:3/62
Modules linked in:
CPU: 3 UID: 0 PID: 62 Comm: kworker/u33:3 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Workqueue: nvme-reset-wq nvme_loop_reset_ctrl_work
RIP: 0010:nvme_loop_reset_ctrl_work+0x1d4/0x620 drivers/nvme/target/loop.c:457
Code: 7c 08 84 d2 0f 85 b2 03 00 00 8b 9b dc f8 ff ff bf 01 00 00 00 83 eb 04 89 de e8 c7 fb 59 fb 83 fb 01 76 09 e8 4d 01 5a fb 90 <0f> 0b 90 e8 44 01 5a fb 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f
RSP: 0018:ffffc900007dfbd8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000000
RDX: ffff888020f72580 RSI: ffffffff86b13ae3 RDI: ffff888020f72580
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000001
R10: 00000000ffffffff R11: 00000000000075fb R12: ffff8880299f83e8
R13: ffff8880299f83ec R14: 0000000000000000 R15: ffff88802886b800
FS:  0000000000000000(0000) GS:ffff888096c67000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000f7f6e210 CR3: 000000004d58f000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396
 process_scheduled_works kernel/workqueue.c:3479 [inline]
 worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560
 kthread+0x373/0x450 kernel/kthread.c:436
 ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>


Tested on:

commit:         940de590 Merge tag 'hardening-v7.3-rc2' of git://git.k..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=116438f9580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=85bc5cc2fc7394d9
dashboard link: https://syzkaller.appspot.com/bug?extid=fefa0af09f7891b1800e
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: i386
patch:          https://syzkaller.appspot.com/x/patch.diff?x=100438f9580000


  reply	other threads:[~2026-09-04  9:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 20:59 [syzbot] [block?] general protection fault in blk_mq_quiesce_queue syzbot
2026-09-04  1:31 ` Edward Adam Davis
2026-09-04  1:57   ` syzbot
2026-09-04  2:38 ` Edward Adam Davis
2026-09-04  3:09   ` syzbot
2026-09-04  4:41 ` Edward Adam Davis
2026-09-04  5:05   ` syzbot
2026-09-04  9:10 ` Edward Adam Davis
2026-09-04  9:33   ` syzbot [this message]
2026-11-10 18:52 ` Forwarded: " syzbot
2026-11-10 18:53 ` syzbot
2026-11-10 18:55 ` syzbot
2026-11-10 18:57 ` syzbot
     [not found] <CAO7_G+zpXKbKY8ggsBsprzCw9M7NSvCyQ-f4KQSM8Etx6GEqKA@mail.gmail.com>
2026-11-10 19:07 ` syzbot
     [not found] <CAO7_G+zVhxDF7obCuC6gyTByFqw7G4fLrSKRRYxpdgt8B-iRig@mail.gmail.com>
2026-11-10 19:19 ` syzbot
     [not found] <CAO7_G+yrCB_-fcq2Fh+pKgYmkd8a7RpCNh1jJgnJ30wHrUSQuQ@mail.gmail.com>
2026-11-10 19:32 ` syzbot
     [not found] <CAO7_G+yzCcvqn1+e0EtEk6=BxyK0yFEZPC7hVU7fma5zk-MnBA@mail.gmail.com>
2026-11-10 19:45 ` 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=6a9a904e.9266084e.bf0d7.060f.GAE@google.com \
    --to=syzbot+fefa0af09f7891b1800e@syzkaller.appspotmail.com \
    --cc=eadavis@sina.com \
    --cc=linux-kernel@vger.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.