* Re: [syzbot] INFO: task hung in rfcomm_process_sessions (2)
[not found] <000000000000b09dc705f3b05f9b@google.com>
@ 2023-02-02 14:01 ` Hillf Danton
0 siblings, 0 replies; only message in thread
From: Hillf Danton @ 2023-02-02 14:01 UTC (permalink / raw)
To: syzbot
Cc: edumazet, linux-bluetooth, linux-kernel, luiz.dentz, marcel,
linux-mm, syzkaller-bugs, yinghsu
On Wed, 01 Feb 2023 20:55:28 -0800
> syzbot suspects this issue was fixed by commit:
>
> commit 1d80d57ffcb55488f0ec0b77928d4f82d16b6a90
> Author: Ying Hsu <yinghsu@chromium.org>
> Date: Wed Jan 11 03:16:14 2023 +0000
>
> Bluetooth: Fix possible deadlock in rfcomm_sk_state_change
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154b77b5480000
> start commit: d888c83fcec7 fs: fix fd table size alignment properly
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=69c8957f4ac2dea6
> dashboard link: https://syzkaller.appspot.com/bug?extid=d761775dff24be3ad4be
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=162ca1fd700000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1036182d700000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: Bluetooth: Fix possible deadlock in rfcomm_sk_state_change
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
If it is the correct fix then why was task hung reported instead of
deadlock? What went wrong with lockdep at cffb2b72d3ed upstream?
Hillf
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-02-02 14:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <000000000000b09dc705f3b05f9b@google.com>
2023-02-02 14:01 ` [syzbot] INFO: task hung in rfcomm_process_sessions (2) Hillf Danton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox