[syzbot] [pci?] WARNING in pci_scan_single_device

[syzbot <syzbot+3385a151582cae2a4b39@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    90b83efa6701 Merge tag 'bpf-next-6.16' of git://git.kernel..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=152307f4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fbd871027e10b130
dashboard link: https://syzkaller.appspot.com/bug?extid=3385a151582cae2a4b39
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7b23158542c6/disk-90b83efa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fe77cd0d7150/vmlinux-90b83efa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fdddbd2ed303/bzImage-90b83efa.xz

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

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fbab67b5fa0 R15: 00007fff54b11b18
 </TASK>
------------[ cut here ]------------
WARNING: CPU: 1 PID: 15983 at drivers/pci/probe.c:2716 pci_device_add+0xf53/0x1390 drivers/pci/probe.c:2716
Modules linked in:
CPU: 1 UID: 0 PID: 15983 Comm: syz.5.1707 Not tainted 6.15.0-syzkaller-07774-g90b83efa6701 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:pci_device_add+0xf53/0x1390 drivers/pci/probe.c:2716
Code: 84 c0 74 06 0f 8e ae 03 00 00 0f b6 83 c0 00 00 00 c1 e5 02 83 e0 e3 09 e8 88 83 c0 00 00 00 e9 de f3 ff ff e8 0e 96 aa fc 90 <0f> 0b 90 e9 81 f8 ff ff e8 00 96 aa fc 90 0f 0b 90 90 0f 0b 90 e9
RSP: 0018:ffffc9001058f918 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000fffffff4 RCX: ffffffff85104754
RDX: ffff88805524da00 RSI: ffffffff85104ed2 RDI: 0000000000000005
RBP: ffff88801b483400 R08: 0000000000000005 R09: 0000000000000000
R10: 00000000fffffff4 R11: ffffffff81000130 R12: ffff888143aa3028
R13: ffff888143aa3000 R14: 0000000000000001 R15: ffff888143abc000
FS:  00007fbab74736c0(0000) GS:ffff888124a82000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f67143b1d58 CR3: 0000000035620000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 pci_scan_single_device drivers/pci/probe.c:2737 [inline]
 pci_scan_single_device+0x325/0x470 drivers/pci/probe.c:2723
 pci_scan_slot+0x1c0/0x790 drivers/pci/probe.c:2820
 pci_scan_child_bus_extend+0x66/0x730 drivers/pci/probe.c:3039
 pci_scan_child_bus drivers/pci/probe.c:3153 [inline]
 pci_rescan_bus+0x18/0x40 drivers/pci/probe.c:3444
 dev_rescan_store+0x11b/0x140 drivers/pci/pci-sysfs.c:479
 dev_attr_store+0x58/0x80 drivers/base/core.c:2440
 sysfs_kf_write+0xef/0x150 fs/sysfs/file.c:145
 kernfs_fop_write_iter+0x354/0x510 fs/kernfs/file.c:334
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x6c7/0x1150 fs/read_write.c:686
 ksys_write+0x12a/0x250 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbab658e969
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbab7473038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fbab67b5fa0 RCX: 00007fbab658e969
RDX: 0000000000000004 RSI: 0000200000000440 RDI: 0000000000000005
RBP: 00007fbab6610ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fbab67b5fa0 R15: 00007fff54b11b18
 </TASK>


---
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