From: syzbot <syzbot+c98b21427617af7f547a@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nvme?] BUG: corrupted list in nvmet_fc_remove_port
Date: Sat, 17 Oct 2026 03:30:01 -0700 [thread overview]
Message-ID: <6ad34e29.6814cce4.34c49f.0055.GAE@google.com> (raw)
In-Reply-To: <20261017092004.650-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: trying to register non-static key in __nvmet_fc_free_assocs
INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
you didn't initialize this object before use?
turning off the locking correctness validator.
CPU: 0 UID: 0 PID: 6854 Comm: syz.0.124 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
assign_lock_key+0x133/0x150 kernel/locking/lockdep.c:1028
register_lock_class+0xcc/0x2e0 kernel/locking/lockdep.c:1343
__lock_acquire+0x10c/0x2de0 kernel/locking/lockdep.c:5162
lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
rt_spin_lock+0x83/0x400 kernel/locking/spinlock_rt.c:56
spin_lock include/linux/spinlock_rt.h:45 [inline]
__nvmet_fc_free_assocs+0x12e/0x430 drivers/nvme/target/fc.c:1492
nvmet_fc_remove_port+0x2b1/0x360 drivers/nvme/target/fc.c:2949
nvmet_disable_port+0x13e/0x1f0 drivers/nvme/target/core.c:400
nvmet_port_subsys_drop_link+0x1e8/0x210 drivers/nvme/target/configfs.c:1123
configfs_unlink+0x44f/0x6b0 fs/configfs/symlink.c:258
vfs_unlink+0x27b/0x6e0 fs/namei.c:5648
filename_unlinkat+0x3d3/0x610 fs/namei.c:5718
__do_sys_unlinkat fs/namei.c:5747 [inline]
__se_sys_unlinkat+0x83/0x1a0 fs/namei.c:5739
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f94beb6e1d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f94be1ad028 EFLAGS: 00000246 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 00007f94bedf6090 RCX: 00007f94beb6e1d9
RDX: 0000000000000000 RSI: 0000200000000780 RDI: ffffffffffffff9c
RBP: 00007f94bec05888 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f94bedf6128 R14: 00007f94bedf6090 R15: 00007ffc099f6dd8
</TASK>
------------[ cut here ]------------
UBSAN: array-index-out-of-bounds in kernel/locking/qspinlock.h:68:9
index 16382 is out of range for type 'unsigned long[8]'
CPU: 0 UID: 0 PID: 6854 Comm: syz.0.124 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
ubsan_epilogue+0xa/0x30 lib/ubsan.c:233
__ubsan_handle_out_of_bounds+0xe8/0xf0 lib/ubsan.c:455
decode_tail kernel/locking/qspinlock.h:68 [inline]
__pv_queued_spin_lock_slowpath+0xaf3/0xbc0 kernel/locking/qspinlock.c:307
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt-spinlock.h:37 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/paravirt-spinlock.h:71 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:115 [inline]
do_raw_spin_lock+0x26c/0x2f0 kernel/locking/spinlock_debug.c:116
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:156 [inline]
_raw_spin_lock_irqsave+0x4c/0x60 kernel/locking/spinlock.c:181
rtlock_slowlock kernel/locking/rtmutex.c:1921 [inline]
rtlock_lock kernel/locking/spinlock_rt.c:43 [inline]
__rt_spin_lock kernel/locking/spinlock_rt.c:49 [inline]
rt_spin_lock+0x157/0x400 kernel/locking/spinlock_rt.c:57
spin_lock include/linux/spinlock_rt.h:45 [inline]
__nvmet_fc_free_assocs+0x12e/0x430 drivers/nvme/target/fc.c:1492
nvmet_fc_remove_port+0x2b1/0x360 drivers/nvme/target/fc.c:2949
nvmet_disable_port+0x13e/0x1f0 drivers/nvme/target/core.c:400
nvmet_port_subsys_drop_link+0x1e8/0x210 drivers/nvme/target/configfs.c:1123
configfs_unlink+0x44f/0x6b0 fs/configfs/symlink.c:258
vfs_unlink+0x27b/0x6e0 fs/namei.c:5648
filename_unlinkat+0x3d3/0x610 fs/namei.c:5718
__do_sys_unlinkat fs/namei.c:5747 [inline]
__se_sys_unlinkat+0x83/0x1a0 fs/namei.c:5739
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f94beb6e1d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f94be1ad028 EFLAGS: 00000246 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 00007f94bedf6090 RCX: 00007f94beb6e1d9
RDX: 0000000000000000 RSI: 0000200000000780 RDI: ffffffffffffff9c
RBP: 00007f94bec05888 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f94bedf6128 R14: 00007f94bedf6090 R15: 00007ffc099f6dd8
</TASK>
---[ end trace ]---
Tested on:
commit: 58161ead Merge tag 'drm-fixes-2026-10-17' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10d88031580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b38d39c45202f4fa
dashboard link: https://syzkaller.appspot.com/bug?extid=c98b21427617af7f547a
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=16d7f67f980000
prev parent reply other threads:[~2026-10-17 10:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 17:32 syzbot
2026-10-12 5:11 ` Hillf Danton
2026-10-12 5:50 ` syzbot
2026-10-12 7:58 ` Hillf Danton
2026-10-12 8:25 ` syzbot
2026-10-12 10:33 ` Hillf Danton
2026-10-12 11:01 ` syzbot
2026-10-12 12:41 ` Hillf Danton
2026-10-12 13:11 ` syzbot
2026-10-17 2:09 ` Hillf Danton
2026-10-17 2:50 ` syzbot
2026-10-17 4:50 ` Nhật Anh Nguyễn Duy
2026-10-17 4:41 ` Hillf Danton
2026-10-17 5:12 ` syzbot
2026-10-17 5:42 ` Hillf Danton
2026-10-17 6:53 ` syzbot
2026-10-17 7:30 ` Hillf Danton
2026-10-17 7:55 ` syzbot
2026-10-17 9:20 ` Hillf Danton
2026-10-17 10:30 ` 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=6ad34e29.6814cce4.34c49f.0055.GAE@google.com \
--to=syzbot+c98b21427617af7f547a@syzkaller.appspotmail.com \
--cc=hdanton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®