Re: [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_exists

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 08d1914293dae38350b8088980e59fbc699a72fe
Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>
Date:   Mon Sep 30 17:26:21 2024 +0000

    Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11bcdb5f980000
start commit:   5847c9777c30 Merge tag 'cgroup-for-6.8-rc7-fixes' of git:/..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=70429b75d4a1a401
dashboard link: https://syzkaller.appspot.com/bug?extid=b69a625d06e8ece26415
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1097b049180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=168a5bde180000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change

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