[v6.1] WARNING in rtnl_dellink

1 view
Skip to first unread message

syzbot

unread,
Mar 21, 2023, 10:27:42 PM3/21/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=14a6225ec80000
kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=aab710bf9cfcdb0236f4
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+aab710...@syzkaller.appspotmail.com

bond0 (unregistering): (slave bond_slave_1): Releasing backup interface
bond0 (unregistering): Released all slaves
------------[ cut here ]------------
WARNING: CPU: 1 PID: 19020 at net/core/dev.c:10865 unregister_netdevice_many+0x13df/0x1870
Modules linked in:
CPU: 1 PID: 19020 Comm: syz-executor.2 Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:unregister_netdevice_many+0x13df/0x1870 net/core/dev.c:10865
Code: 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 05 95 f8 bc 05 01 48 c7 c7 60 39 e0
RSP: 0018:ffffc90003b2ef40 EFLAGS: 00010287
RAX: ffffffff8882084f RBX: ffff88807e9200b0 RCX: 0000000000040000
RDX: ffffc9000af01000 RSI: 0000000000022d83 RDI: 0000000000022d84
RBP: ffffc90003b2f0b0 R08: ffffffff888207a8 R09: fffffbfff1c12075
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100fd24181 R14: ffff88807e920000 R15: ffff888020ade780
FS: 00007f9bb3133700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f71e79ad988 CR3: 0000000077eed000 CR4: 00000000003526e0
Call Trace:
<TASK>
rtnl_delete_link net/core/rtnetlink.c:3123 [inline]
rtnl_dellink+0x4e1/0x880 net/core/rtnetlink.c:3174
rtnetlink_rcv_msg+0x776/0xf00 net/core/rtnetlink.c:6091
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2550
netlink_unicast_kernel net/netlink/af_netlink.c:1328 [inline]
netlink_unicast+0x7bf/0x990 net/netlink/af_netlink.c:1354
netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:716 [inline]
sock_sendmsg net/socket.c:736 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2482
___sys_sendmsg net/socket.c:2536 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2565
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f9bb248c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9bb3133168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f9bb25abf80 RCX: 00007f9bb248c0f9
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 00007f9bb24e7b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd4ed5889f R14: 00007f9bb3133300 R15: 0000000000022000
</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,
Jul 19, 2023, 10:27:45 PM7/19/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages