[syzbot] [net?] upstream boot error: KMSAN: uninit-value in stack_depot_save_flags

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b555d191561a Merge tag 'perf-tools-fixes-for-v6.8-1-2024-0..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11560a38180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c11709bae75cc702
dashboard link: https://syzkaller.appspot.com/bug?extid=d3af3bd3dc5f4d43ba10
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ab88ac39d951/disk-b555d191.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/53de6d54d856/vmlinux-b555d191.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0154e4e3e071/bzImage-b555d191.xz

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

io scheduler kyber registered
io scheduler bfq registered
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
ACPI: button: Power Button [PWRF]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input1
ACPI: button: Sleep Button [SLPF]
ioatdma: Intel(R) QuickData Technology Driver 5.00
ACPI: \_SB_.LNKC: Enabled at IRQ 11
virtio-pci 0000:00:03.0: virtio_pci: leaving for legacy driver
ACPI: \_SB_.LNKD: Enabled at IRQ 10
virtio-pci 0000:00:04.0: virtio_pci: leaving for legacy driver
ACPI: \_SB_.LNKB: Enabled at IRQ 10
virtio-pci 0000:00:06.0: virtio_pci: leaving for legacy driver
virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver
N_HDLC line discipline registered with maxframe=4096
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
00:04: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
00:05: ttyS2 at I/O 0x3e8 (irq = 6, base_baud = 115200) is a 16550A
00:06: ttyS3 at I/O 0x2e8 (irq = 7, base_baud = 115200) is a 16550A
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
ACPI: bus type drm_connector registered
[drm] Initialized vgem 1.0.0 20120112 for vgem on minor 0
[drm] Initialized vkms 1.0.0 20180514 for vkms on minor 1
Console: switching to colour frame buffer device 128x48
platform vkms: [drm] fb0: vkmsdrmfb frame buffer device
usbcore: registered new interface driver udl
brd: module loaded
loop: module loaded
zram: Added device: zram0
null_blk: disk nullb0 created
null_blk: module loaded
Guest personality initialized and is inactive
VMCI host device registered (name=vmci, major=10, minor=118)
Initialized host personality
usbcore: registered new interface driver rtsx_usb
usbcore: registered new interface driver viperboard
usbcore: registered new interface driver dln2
usbcore: registered new interface driver pn533_usb
nfcsim 0.2 initialized
usbcore: registered new interface driver port100
usbcore: registered new interface driver nfcmrvl
Loading iSCSI transport class v2.0-870.
virtio_scsi virtio0: 1/0/0 default/read/poll queues
scsi host0: Virtio SCSI HBA
st: Version 20160209, fixed bufsize 32768, s/g segs 256
Rounding down aligned max_sectors from 4294967295 to 4294967288
db_root: cannot open: /etc/target
=====================================================
BUG: KMSAN: uninit-value in __list_del_entry_valid_or_report+0x19e/0x490 lib/list_debug.c:52
__list_del_entry_valid_or_report+0x19e/0x490 lib/list_debug.c:52
__list_del_entry_valid include/linux/list.h:124 [inline]
__list_del_entry include/linux/list.h:215 [inline]
list_del include/linux/list.h:229 [inline]
depot_pop_free lib/stackdepot.c:426 [inline]
depot_alloc_stack lib/stackdepot.c:445 [inline]
stack_depot_save_flags+0x3e9/0x7b0 lib/stackdepot.c:684
stack_depot_save+0x12/0x20 lib/stackdepot.c:722
ref_tracker_alloc+0x215/0x700 lib/ref_tracker.c:210
__netdev_tracker_alloc include/linux/netdevice.h:4147 [inline]
netdev_hold include/linux/netdevice.h:4176 [inline]
linkwatch_add_event net/core/link_watch.c:127 [inline]
linkwatch_fire_event+0x32b/0x6d0 net/core/link_watch.c:292
netif_carrier_off+0xec/0x110 net/sched/sch_generic.c:601
bond_create+0x19d/0x2a0 drivers/net/bonding/bond_main.c:6396
bonding_init+0x1a7/0x2d0 drivers/net/bonding/bond_main.c:6474
do_one_initcall+0x216/0x960 init/main.c:1236
do_initcall_level+0x140/0x350 init/main.c:1298
do_initcalls+0xf0/0x1d0 init/main.c:1314
do_basic_setup+0x22/0x30 init/main.c:1333
kernel_init_freeable+0x300/0x4b0 init/main.c:1551
kernel_init+0x2f/0x7e0 init/main.c:1441
ret_from_fork+0x66/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

Uninit was created at:
__alloc_pages+0x9a6/0xe00 mm/page_alloc.c:4590
alloc_pages_mpol+0x62b/0x9d0 mm/mempolicy.c:2133
alloc_pages+0x1be/0x1e0 mm/mempolicy.c:2204
stack_depot_save_flags+0x73e/0x7b0 lib/stackdepot.c:672
stack_depot_save+0x12/0x20 lib/stackdepot.c:722
ref_tracker_alloc+0x215/0x700 lib/ref_tracker.c:210
__netdev_tracker_alloc include/linux/netdevice.h:4147 [inline]
netdev_hold+0xe2/0x120 include/linux/netdevice.h:4176
register_netdevice+0x1c34/0x2230 net/core/dev.c:10281
bond_create+0x138/0x2a0 drivers/net/bonding/bond_main.c:6390
bonding_init+0x1a7/0x2d0 drivers/net/bonding/bond_main.c:6474
do_one_initcall+0x216/0x960 init/main.c:1236
do_initcall_level+0x140/0x350 init/main.c:1298
do_initcalls+0xf0/0x1d0 init/main.c:1314
do_basic_setup+0x22/0x30 init/main.c:1333
kernel_init_freeable+0x300/0x4b0 init/main.c:1551
kernel_init+0x2f/0x7e0 init/main.c:1441
ret_from_fork+0x66/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-rc2-syzkaller-00419-gb555d191561a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
=====================================================


---
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 syzk...@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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.