The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+18b6b27f58e98c240814@syzkaller.appspotmail.com>
To: cassel@kernel.org, hch@lst.de, justin.tee@broadcom.com,
	kch@nvidia.com,  linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org,  nareshgottumukkala83@gmail.com,
	paul.ely@broadcom.com, sagi@grimberg.me,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nvme?] WARNING in nvmet_fc_register_targetport
Date: Thu, 13 Aug 2026 01:42:37 -0700	[thread overview]
Message-ID: <6a7d837d.c5ad36c8.12f49d.002c.GAE@google.com> (raw)
In-Reply-To: <6a7bbaa4.a2bb2777.31c27d.000b.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    3d6d817622b0 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1119f479580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
dashboard link: https://syzkaller.appspot.com/bug?extid=18b6b27f58e98c240814
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=174e8ac6580000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+18b6b27f58e98c240814@syzkaller.appspotmail.com

R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000003
R13: 00007fe0eeb9c063 R14: 00007fe0eebc6cc0 R15: 0000000000000002
 </TASK>
------------[ cut here ]------------
!PageLargeKmalloc(page)
WARNING: mm/slub.c:6602 at free_large_kmalloc+0xbf/0x100 mm/slub.c:6602, CPU#2: syz-executor838/6035
Modules linked in:
CPU: 2 UID: 0 PID: 6035 Comm: syz-executor838 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
RIP: 0010:free_large_kmalloc+0xbf/0x100 mm/slub.c:6602
Code: 28 90 0f 0b 90 80 3d f7 c8 9a 0e 00 0f 84 87 b4 b5 fe 48 8b 74 24 28 48 89 ef e8 8c 3b 0c 00 b8 00 f0 ff ff 45 31 ed eb 9d 90 <0f> 0b 90 48 83 c4 08 48 89 df 48 c7 c6 53 4d 19 8e 5b 5d 41 5c 41
RSP: 0018:ffffc9000347fa28 EFLAGS: 00010202
RAX: 00000000000000ff RBX: ffffea00016377c0 RCX: 000000000000002e
RDX: 0000000000000000 RSI: ffff888058ddff20 RDI: ffffea00016377c0
RBP: ffff888058ddff20 R08: ffff888052911000 R09: 00000000ffffffff
R10: ffffffffffffffff R11: 0000000000000000 R12: 00000000ffffffff
R13: 1ffff9200068ff5e R14: dead000000000122 R15: ffff888058ddff30
FS:  000055557f333400(0000) GS:ffff8880d5fec000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055557f335768 CR3: 0000000058747000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 nvmet_fc_alloc_ls_iodlist drivers/nvme/target/fc.c:569 [inline]
 nvmet_fc_register_targetport+0x114c/0x1c30 drivers/nvme/target/fc.c:1411
 fcloop_create_target_port+0x156/0x5a0 drivers/nvme/target/fcloop.c:1558
 dev_attr_store+0x58/0x80 drivers/base/core.c:2505
 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145
 kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x6ac/0x1050 fs/read_write.c:687
 ksys_write+0x12a/0x250 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe0eeb63277
Code: 48 89 fa 4c 89 df e8 98 1d 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
RSP: 002b:00007fffdd23d920 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000055557f333400 RCX: 00007fe0eeb63277
RDX: 000000000000002f RSI: 00007fffdd23d970 RDI: 0000000000000003
RBP: 00007fffdd23d970 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000003
R13: 00007fe0eeb9c063 R14: 00007fe0eebc6cc0 R15: 0000000000000002
 </TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

      parent reply	other threads:[~2026-08-13  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12  0:13 [syzbot] [nvme?] WARNING in nvmet_fc_register_targetport syzbot
2026-08-12 16:54 ` Niklas Cassel
2026-08-13  8:42 ` 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=6a7d837d.c5ad36c8.12f49d.002c.GAE@google.com \
    --to=syzbot+18b6b27f58e98c240814@syzkaller.appspotmail.com \
    --cc=cassel@kernel.org \
    --cc=hch@lst.de \
    --cc=justin.tee@broadcom.com \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nareshgottumukkala83@gmail.com \
    --cc=paul.ely@broadcom.com \
    --cc=sagi@grimberg.me \
    --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