syzbot


possible deadlock in team_device_event

Status: upstream: reported on 2025/10/05 03:00
Reported-by: syzbot+4b93c981a8b75227635d@syzkaller.appspotmail.com
First crash: 128d, last: 4d12h
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in team_device_event net 4 30 1987d 2054d 0/29 auto-closed as invalid on 2020/12/31 13:59
upstream possible deadlock in team_device_event (3) net 4 C error 38569 170d 641d 29/29 fixed on 2025/09/04 16:57
upstream possible deadlock in team_device_event (2) net 4 8 1534d 1770d 0/29 auto-closed as invalid on 2022/03/29 04:55
linux-5.15 possible deadlock in team_device_event 4 1 119d 119d 0/3 auto-obsoleted due to no activity on 2026/01/21 16:55

Sample crash report:
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.4.3476/18055 is trying to acquire lock:
ffff888031990d00 (team->team_lock_key#5){+.+.}-{3:3}, at: team_port_change_check drivers/net/team/team.c:3007 [inline]
ffff888031990d00 (team->team_lock_key#5){+.+.}-{3:3}, at: team_device_event+0x18a/0xa20 drivers/net/team/team.c:3033

but task is already holding lock:
ffff888031990d00 (team->team_lock_key#5){+.+.}-{3:3}, at: team_del_slave+0x32/0x1c0 drivers/net/team/team.c:1997

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(team->team_lock_key#5);
  lock(team->team_lock_key#5);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

2 locks held by syz.4.3476/18055:
 #0: ffffffff8e3c0308 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:78 [inline]
 #0: ffffffff8e3c0308 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x811/0xfa0 net/core/rtnetlink.c:6469
 #1: ffff888031990d00 (team->team_lock_key#5){+.+.}-{3:3}, at: team_del_slave+0x32/0x1c0 drivers/net/team/team.c:1997

stack backtrace:
CPU: 0 PID: 18055 Comm: syz.4.3476 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x5dbc/0x7d40 kernel/locking/lockdep.c:5137
 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x136/0xcc0 kernel/locking/mutex.c:747
 team_port_change_check drivers/net/team/team.c:3007 [inline]
 team_device_event+0x18a/0xa20 drivers/net/team/team.c:3033
 notifier_call_chain+0x197/0x380 kernel/notifier.c:93
 call_netdevice_notifiers_extack net/core/dev.c:2103 [inline]
 call_netdevice_notifiers net/core/dev.c:2117 [inline]
 dev_close_many+0x2a9/0x410 net/core/dev.c:1658
 vlan_device_event+0x1811/0x1f10 net/8021q/vlan.c:476
 notifier_call_chain+0x197/0x380 kernel/notifier.c:93
 call_netdevice_notifiers_extack net/core/dev.c:2103 [inline]
 call_netdevice_notifiers net/core/dev.c:2117 [inline]
 dev_close_many+0x2a9/0x410 net/core/dev.c:1658
 dev_close+0x158/0x210 net/core/dev.c:1680
 team_port_del+0x4e0/0xc80 drivers/net/team/team.c:1366
 team_del_slave+0x3d/0x1c0 drivers/net/team/team.c:1998
 do_set_master net/core/rtnetlink.c:2692 [inline]
 do_setlink+0xe7f/0x4130 net/core/rtnetlink.c:2912
 rtnl_group_changelink net/core/rtnetlink.c:3454 [inline]
 __rtnl_newlink net/core/rtnetlink.c:3713 [inline]
 rtnl_newlink+0x1148/0x20a0 net/core/rtnetlink.c:3750
 rtnetlink_rcv_msg+0x869/0xfa0 net/core/rtnetlink.c:6472
 netlink_rcv_skb+0x241/0x4d0 net/netlink/af_netlink.c:2545
 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
 netlink_unicast+0x751/0x8d0 net/netlink/af_netlink.c:1346
 netlink_sendmsg+0x8d0/0xbf0 net/netlink/af_netlink.c:1894
 sock_sendmsg_nosec net/socket.c:730 [inline]
 __sock_sendmsg net/socket.c:745 [inline]
 ____sys_sendmsg+0x5ba/0x960 net/socket.c:2594
 ___sys_sendmsg+0x2a6/0x360 net/socket.c:2648
 __sys_sendmsg net/socket.c:2677 [inline]
 __do_sys_sendmsg net/socket.c:2686 [inline]
 __se_sys_sendmsg+0x1c2/0x2b0 net/socket.c:2684
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fbbf559aeb9
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:00007fbbf6457028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fbbf5816090 RCX: 00007fbbf559aeb9
RDX: 0000000000000000 RSI: 0000200000000280 RDI: 0000000000000005
RBP: 00007fbbf5608c1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fbbf5816128 R14: 00007fbbf5816090 R15: 00007ffdbc1e7da8
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/06 01:48 linux-6.6.y 2cf6f68313dc f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in team_device_event
2025/10/30 22:14 linux-6.6.y e5bbb12db2c7 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in team_device_event
2025/10/15 22:23 linux-6.6.y 0bbbd97a442d 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in team_device_event
2025/10/05 02:59 linux-6.6.y f34f16e5c632 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in team_device_event
* Struck through repros no longer work on HEAD.