[v5.15] WARNING in default_device_exit_batch

8 views
Skip to first unread message

syzbot

unread,
Mar 17, 2023, 10:46:50 AM3/17/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15bf3976c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=29d2c94444abfa53133f
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/857e17de0f0a/disk-8020ae3c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9efc49fcd441/vmlinux-8020ae3c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f14c38b6bfa7/bzImage-8020ae3c.xz

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

bond5 (unregistering): Released all slaves
bond4 (unregistering): Released all slaves
bond0 (unregistering): (slave bond3): Releasing backup interface
bond3 (unregistering): Released all slaves
bond2 (unregistering): Released all slaves
bond1 (unregistering): Released all slaves
------------[ cut here ]------------
WARNING: CPU: 0 PID: 144 at net/core/dev.c:11088 unregister_netdevice_many+0x13f0/0x18f0
Modules linked in:
CPU: 0 PID: 144 Comm: kworker/u4:1 Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: netns cleanup_net
RIP: 0010:unregister_netdevice_many+0x13f0/0x18f0 net/core/dev.c:11088
Code: 8f f9 48 8b 7c 24 28 48 8b 3f 48 3b 7c 24 10 0f 84 ed 00 00 00 48 89 fb e8 bd 19 46 f9 48 89 d9 e9 c7 f6 ff ff e8 b0 19 46 f9 <0f> 0b e9 4e ff ff ff e8 a4 19 46 f9 0f 0b eb 9e e8 9b 19 46 f9 c6
RSP: 0018:ffffc9000174f8c0 EFLAGS: 00010293
RAX: ffffffff883a5f20 RBX: ffff88804412c0a0 RCX: ffff888016e19d00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000174fa50 R08: ffffffff883a5e28 R09: fffffbfff1b3b201
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100882598a R14: ffff88804412c000 R15: ffff888045a04200
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f826dd57300 CR3: 00000000235fc000 CR4: 00000000003506f0
Call Trace:
<TASK>
default_device_exit_batch+0x390/0x3f0 net/core/dev.c:11594
ops_exit_list net/core/net_namespace.c:174 [inline]
cleanup_net+0x763/0xb60 net/core/net_namespace.c:596
process_one_work+0x90d/0x1270 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Mar 20, 2023, 7:21:39 PM3/20/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12134f16c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=92149adf6d6d4fdcb4ce
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/610a00ba4375/disk-7eaef76f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57c1310f9a30/vmlinux-7eaef76f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81999f717d3b/bzImage-7eaef76f.xz

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

device veth1_macvtap left promiscuous mode
device veth0_macvtap left promiscuous mode
device veth1_vlan left promiscuous mode
bond4 (unregistering): Released all slaves
bond3 (unregistering): Released all slaves
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3944 at net/core/dev.c:10864 unregister_netdevice_many+0x13d3/0x1870
Modules linked in:
CPU: 0 PID: 3944 Comm: kworker/u4:9 Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: netns cleanup_net
RIP: 0010:unregister_netdevice_many+0x13d3/0x1870 net/core/dev.c:10864
Code: 5e f9 48 8b 7c 24 20 48 8b 3f 48 3b 7c 24 10 0f 84 ed 00 00 00 48 89 fb e8 ea 58 08 f9 48 89 d9 e9 ba f6 ff ff e8 dd 58 08 f9 <0f> 0b e9 4e ff ff ff e8 d1 58 08 f9 0f 0b eb 9e e8 c8 58 08 f9 c6
RSP: 0018:ffffc90005a7f900 EFLAGS: 00010293
RAX: ffffffff88820843 RBX: ffff8880223a80a0 RCX: ffff888023c59d40
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90005a7fa70 R08: ffffffff8882074b R09: fffffbfff1c12075
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff11004475181 R14: ffff8880223a8000 R15: ffff88801dd7d880
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f086aa1ea70 CR3: 000000000cc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
default_device_exit_batch+0x5bc/0x630 net/core/dev.c:11335
ops_exit_list net/core/net_namespace.c:174 [inline]
cleanup_net+0x763/0xb60 net/core/net_namespace.c:601
process_one_work+0x909/0x1380 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x268/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

syzbot

unread,
Jul 15, 2023, 10:46:51 AM7/15/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.

syzbot

unread,
Jul 19, 2023, 1:51:37 PM7/19/23
to syzkaller...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages