From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+d761775dff24be3ad4be@syzkaller.appspotmail.com>
Cc: edumazet@google.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, yinghsu@chromium.org
Subject: Re: [syzbot] INFO: task hung in rfcomm_process_sessions (2)
Date: Thu, 2 Feb 2023 22:01:30 +0800 [thread overview]
Message-ID: <20230202140130.828-1-hdanton@sina.com> (raw)
In-Reply-To: <000000000000b09dc705f3b05f9b@google.com>
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
parent reply other threads:[~2023-02-02 14:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000b09dc705f3b05f9b@google.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230202140130.828-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=edumazet@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=syzbot+d761775dff24be3ad4be@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yinghsu@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox