From: syzbot <syzbot+87bb32e345aa80c0554b@syzkaller.appspotmail.com>
To: bhelgaas@google.com, kapoorarnav43@gmail.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [pci?] WARNING in pci_scan_single_device (2)
Date: Fri, 24 Jul 2026 15:31:35 -0700 [thread overview]
Message-ID: <6a63e7c7.70955b6c.323240.000b.GAE@google.com> (raw)
In-Reply-To: <697018fc.050a0220.706b.0003.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 48a5a7ab8d6a Merge tag 'v7.2-rc4-smb3-client-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c02499580000
kernel config: https://syzkaller.appspot.com/x/.config?x=145fa60d73086782
dashboard link: https://syzkaller.appspot.com/bug?extid=87bb32e345aa80c0554b
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1677d746580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=158932ea580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-48a5a7ab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8ed725bee82f/vmlinux-48a5a7ab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/110c09c210d5/bzImage-48a5a7ab.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+87bb32e345aa80c0554b@syzkaller.appspotmail.com
</TASK>
pci (null): [8086:2934] type 00 class 0x0c0300 conventional PCI endpoint
pci (null): BAR 4 [io 0xc0e0-0xc0ff]
------------[ cut here ]------------
ret < 0
WARNING: drivers/pci/probe.c:2768 at pci_device_add+0x133b/0x1810 drivers/pci/probe.c:2768, CPU#1: syz.0.17/5936
Modules linked in:
CPU: 1 UID: 0 PID: 5936 Comm: syz.0.17 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:pci_device_add+0x133b/0x1810 drivers/pci/probe.c:2768
Code: e5 04 83 e0 8f 09 e8 88 83 c8 00 00 00 e9 28 f4 ff ff e8 18 a3 ae fc 90 0f 0b 90 90 0f 0b 90 e9 0e f7 ff ff e8 06 a3 ae fc 90 <0f> 0b 90 e9 7e fa ff ff e8 f8 a2 ae fc 90 0f 0b 90 e9 11 fa ff ff
RSP: 0018:ffffc900037a7928 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000ffffffea RCX: ffffffff855bb419
RDX: ffff888025a72540 RSI: ffffffff855bb99a RDI: ffff888025a72540
RBP: ffff88801c2e9000 R08: 0000000000000005 R09: 0000000000000000
R10: 00000000ffffffea R11: 0000000000000000 R12: ffff888022e6f028
R13: ffff888022e6f000 R14: 0000000000000001 R15: ffff888022e92000
FS: 0000555591741500(0000) GS:ffff8880d5ede000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055af1cf515a8 CR3: 000000003dca4000 CR4: 0000000000352ef0
Call Trace:
<TASK>
pci_scan_single_device drivers/pci/probe.c:2792 [inline]
pci_scan_single_device+0x1d0/0x240 drivers/pci/probe.c:2778
pci_scan_slot+0x1c9/0x7c0 drivers/pci/probe.c:2875
pci_scan_child_bus_extend+0x6b/0x7b0 drivers/pci/probe.c:3094
pci_scan_child_bus drivers/pci/probe.c:3207 [inline]
pci_rescan_bus+0x18/0x40 drivers/pci/probe.c:3498
rescan_store+0xfb/0x130 drivers/pci/pci-sysfs.c:473
bus_attr_store+0x74/0xb0 drivers/base/bus.c:172
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:0x7fe44799de99
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:00007ffce5639058 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fe447c25fa0 RCX: 00007fe44799de99
RDX: 0000000000000001 RSI: 0000200000000800 RDI: 0000000000000004
RBP: 00007ffce56390c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fe447c25fac R14: 00007fe447c25fa0 R15: 00007fe447c25fa0
</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.
next prev parent reply other threads:[~2026-07-24 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 0:08 syzbot
2026-07-24 22:31 ` syzbot [this message]
2026-07-25 10:06 ` Forwarded: [PATCH] PCI: Handle dev_set_name() failure in pci_setup_device() syzbot
[not found] <20260725100645.221918-1-rihyeon8648@gmail.com>
2026-07-25 10:32 ` [syzbot] [pci?] WARNING in pci_scan_single_device (2) 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=6a63e7c7.70955b6c.323240.000b.GAE@google.com \
--to=syzbot+87bb32e345aa80c0554b@syzkaller.appspotmail.com \
--cc=bhelgaas@google.com \
--cc=kapoorarnav43@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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®