Re: [syzbot] [net?] possible deadlock in team_port_change_check (2)

[syzbot]

syzbot has bisected this issue to:

commit ec4ffd100ffb396eca13ebe7d18938ea80f399c3
Author: Nicolas Dichtel <nicolas.dichtel@xxxxxxxxx>
Date:   Mon Jan 8 09:41:02 2024 +0000

    Revert "net: rtnetlink: Enslave device before bringing it up"

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=163d5686180000
start commit:   90d35da658da Linux 6.8-rc7
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=153d5686180000
console output: https://syzkaller.appspot.com/x/log.txt?x=113d5686180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c11c5c676adb61f0
dashboard link: https://syzkaller.appspot.com/bug?extid=3c47b5843403a45aef57
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=158ae1de180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=165f2732180000

Reported-by: syzbot+3c47b5843403a45aef57@xxxxxxxxxxxxxxxxxxxxxxxxx
Fixes: ec4ffd100ffb ("Revert "net: rtnetlink: Enslave device before bringing it up"")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection