linux-kernel - Re: [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6739f797.050a0220.87769.000f.GAE@google.com>
Date: Sun, 17 Nov 2024 06:03:03 -0800
From: syzbot <syzbot+b69a625d06e8ece26415@...kaller.appspotmail.com>
To: axboe@...nel.dk, davem@...emloft.net, edumazet@...gle.com, 
	hdanton@...a.com, johan.hedberg@...il.com, kuba@...nel.org, 
	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org, 
	luiz.dentz@...il.com, luiz.von.dentz@...el.com, marcel@...tmann.org, 
	netdev@...r.kernel.org, pabeni@...hat.com, syzkaller-bugs@...glegroups.com, 
	yangyingliang@...wei.com
Subject: Re: [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_exists

syzbot suspects this issue was fixed by commit:

commit 08d1914293dae38350b8088980e59fbc699a72fe
Author: Luiz Augusto von Dentz <luiz.von.dentz@...el.com>
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