netlink: 'syz-executor.0': attribute type 10 has an invalid length.
team0: Port device vlan1 added
netlink: 'syz-executor.0': attribute type 10 has an invalid length.
veth0_vlan: left promiscuous mode
veth0_vlan: entered promiscuous mode
============================================
WARNING: possible recursive locking detected
6.7.0-syzkaller #0 Not tainted
--------------------------------------------
syz-executor.0/5705 is trying to acquire lock:
ffff888115a5ad00 (team->team_lock_key){+.+.}-{3:3}, at: team_port_change_check+0x23/0xc0 drivers/net/team/team.c:2997

but task is already holding lock:
ffff888115a5ad00 (team->team_lock_key){+.+.}-{3:3}, at: team_add_slave+0x47/0x11d0 drivers/net/team/team.c:1974

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

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

 *** DEADLOCK ***

 May be due to missing lock nesting notation

2 locks held by syz-executor.0/5705:
 #0: ffffffff87a83a18 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:79 [inline]
 #0: ffffffff87a83a18 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x51f/0xa30 net/core/rtnetlink.c:6612
 #1: ffff888115a5ad00 (team->team_lock_key){+.+.}-{3:3}, at: team_add_slave+0x47/0x11d0 drivers/net/team/team.c:1974

stack backtrace:
CPU: 1 PID: 5705 Comm: syz-executor.0 Not tainted 6.7.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xfe/0x190 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x10be/0x2490 kernel/locking/lockdep.c:5137
 lock_acquire+0xea/0x270 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x99/0x9a0 kernel/locking/mutex.c:752
 team_port_change_check+0x23/0xc0 drivers/net/team/team.c:2997
 team_device_event+0x2da/0x300 drivers/net/team/team.c:3020
 notifier_call_chain+0xd6/0x230 kernel/notifier.c:93
 __dev_notify_flags+0x15f/0x250
 dev_change_flags+0x70/0x90 net/core/dev.c:8725
 vlan_device_event+0xc60/0xda0 net/8021q/vlan.c:468
 notifier_call_chain+0xd6/0x230 kernel/notifier.c:93
 call_netdevice_notifiers_info net/core/dev.c:1966 [inline]
 call_netdevice_notifiers_extack net/core/dev.c:2004 [inline]
 call_netdevice_notifiers net/core/dev.c:2018 [inline]
 dev_open+0xe7/0x130 net/core/dev.c:1487
 team_port_add drivers/net/team/team.c:1215 [inline]
 team_add_slave+0x487/0x11d0 drivers/net/team/team.c:1975
 do_set_master net/core/rtnetlink.c:2704 [inline]
 do_setlink+0x743/0x1e70 net/core/rtnetlink.c:2910
 rtnl_setlink+0x2fa/0x350 net/core/rtnetlink.c:3206
 rtnetlink_rcv_msg+0x55d/0xa30 net/core/rtnetlink.c:6615
 netlink_rcv_skb+0xe8/0x1c0 net/netlink/af_netlink.c:2543
 netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]
 netlink_unicast+0x488/0x550 net/netlink/af_netlink.c:1367
 netlink_sendmsg+0x588/0x670 net/netlink/af_netlink.c:1908
 sock_sendmsg_nosec net/socket.c:730 [inline]
 __sock_sendmsg+0xca/0xf0 net/socket.c:745
 sock_write_iter+0x18b/0x1e0 net/socket.c:1160
 vfs_writev+0x554/0x840 fs/read_write.c:971
 do_writev+0xcf/0x1c0 fs/read_write.c:1018
 do_syscall_64+0xa7/0x1c0
 entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7f7920c7dda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7921a870c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 00007f7920dabf80 RCX: 00007f7920c7dda9
RDX: 0000000000000001 RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00007f7920cca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f7920dabf80 R15: 00007ffee4197f18
 </TASK>