From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f208.google.com (mail-oi1-f208.google.com [209.85.167.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1B238280338 for ; Wed, 12 Aug 2026 00:13:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.208 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786493606; cv=none; b=eD6LRCqyvxiw2vwCKwmB57HehW31VmIcWrVjsHnA86nMN5XRbH+Fz+RpuNCj+sJf6mpwubD3BxLKetfvDucIHbInWm0kvXqhH6acXdfps7JRrCsZ9nMPpb5Iuj3h9oGki+91l5KLEKWFDwnCVaUcspj9Sr9UGlXaQPjGMX1WClU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786493606; c=relaxed/simple; bh=G9t+QlIgYjbRUOxlAsQqMTZZOJ4t6As0pc0XnHzyskg=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=R2QJ7g5MQeYenPREU+EyUUbsuV0Ui11zWyS/fE78Vm7GKcTmh5xYbytpGsB6jtVaogFaqSfwolFOc1gxDB6V9iDNLvVHmlZykZqhFY0iKSu1SGty3WGloj0e/GJI8fiQtHaz5mIBvq3OJfuusIAIOYUC5XIGs9NdmUIJjjO/hyc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.208 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi1-f208.google.com with SMTP id 5614622812f47-4a49f09233fso372503b6e.0 for ; Tue, 11 Aug 2026 17:13:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786493604; x=1787098404; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=ALvRCc5w+8E9Jm2AZEz/0T3ZiCqnoqzvERWPEGTrbw4=; b=RYAAXE+Yoq12fCxK5McdW6L19qMKZ5jIoKS9dTB2Tf5P5ryds2jHSTMe/J7fzhWFa5 X6sR4npGR7GHXxlw1a4y/WfbDPbtUj2oaqyMUvuFZ4H9gPN/VrAm/rovVoQuf7bNk3gC EFF2InTK9bR63v+atnI5Ezd7JimOrxDBQYYOwJUtAKqy6KMX+MmYI5Qn8SP4na8QjohJ yVAla7Pfl0Od+9yrXdpsyUItwIXQ/SzU6yFdWuXDSzn8ZA6dQXjJw9uwfCJBJNYVrFNE LoZlfT98R1mT6Iwwr5ZbNM7dxU/cf7GZvohItIM07BekBb9QqqLs+HZ2joOupB8K5B6s CgqQ== X-Forwarded-Encrypted: i=1; AHgh+RoQnfOoI0q1qnkv07J88K8/7xlWrEdn3YOohqn7PA41vuya5T8IO3qLF3TIWCr9tNjcibR4nCwtht5KVd4=@vger.kernel.org X-Gm-Message-State: AOJu0YyEtOdAznuSuReSYBn1DixtgtbK0sez18MLHY9WIFwDudVeooOl 0Iu+XMxPlyDmrMuEnv4SNAYUKp3NpmrqCPAADjLX730xOKFDaI8KkQEis0zMElqT/WVjsoCOuDb 7/1tAhR12PYW2hvywME4KE1/QE5GoBZ+igzk6HIRXC0fXI5xLLyPzrzG2XFo= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:3a06:b0:495:ca1b:7865 with SMTP id 5614622812f47-4b20900f206mr3554396b6e.11.1786493604057; Tue, 11 Aug 2026 17:13:24 -0700 (PDT) Date: Tue, 11 Aug 2026 17:13:24 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a7bbaa4.a2bb2777.31c27d.000b.GAE@google.com> Subject: [syzbot] [nvme?] WARNING in nvmet_fc_register_targetport From: syzbot To: 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 Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: f9a2394a2348 Merge tag 'mm-hotfixes-stable-2026-08-06-18-4.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12e68fb9580000 kernel config: https://syzkaller.appspot.com/x/.config?x=e3f9a6906b632f9f 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 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-f9a2394a.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/969d729dd37f/vmlinux-f9a2394a.xz kernel image: https://storage.googleapis.com/syzbot-assets/a948a2342c62/bzImage-f9a2394a.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+18b6b27f58e98c240814@syzkaller.appspotmail.com R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 ------------[ cut here ]------------ !PageLargeKmalloc(page) WARNING: mm/slub.c:6602 at free_large_kmalloc+0xbf/0x100 mm/slub.c:6602, CPU#0: syz.2.261/6867 Modules linked in: CPU: 0 UID: 0 PID: 6867 Comm: syz.2.261 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 e8 ab 9c 0e 00 0f 84 c7 6e b7 fe 48 8b 74 24 28 48 89 ef e8 7c 3a 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 24 df 18 8e 5b 5d 41 5c 41 RSP: 0018:ffffc9000735fa10 EFLAGS: 00010202 RAX: 00000000000000ff RBX: ffffea00017e83c0 RCX: 000000000000002e RDX: 0000000000000000 RSI: ffff88805fa0ff20 RDI: ffffea00017e83c0 RBP: ffff88805fa0ff20 R08: ffff888023ddfc00 R09: 00000000ffffffff R10: ffffffffffffffff R11: 0000000000000000 R12: 00000000ffffffff R13: 1ffff92000e6bf5b R14: dead000000000122 R15: ffff888023ddfc90 FS: 0000000000000000(0000) GS:ffff888096bf4000(0063) knlGS:00000000f5456b40 CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000025d36000 CR4: 0000000000352ef0 Call Trace: 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_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline] __do_fast_syscall_32+0xe7/0x970 arch/x86/entry/syscall_32.c:307 do_fast_syscall_32+0x32/0x70 arch/x86/entry/syscall_32.c:332 entry_SYSENTER_compat_after_hwframe+0x84/0x8e RIP: 0023:0xf7f96fec Code: Unable to access opcode bytes at 0xf7f96fc2. RSP: 002b:00000000f545650c EFLAGS: 00000292 ORIG_RAX: 0000000000000004 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000080000200 RDX: 000000000000002f RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup