From: syzbot <syzbot+d761775dff24be3ad4be@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org, netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, yinghsu@chromium.org
Subject: Re: [syzbot] INFO: task hung in rfcomm_process_sessions (2)
Date: Wed, 01 Feb 2023 20:55:28 -0800 [thread overview]
Message-ID: <000000000000b09dc705f3b05f9b@google.com> (raw)
In-Reply-To: <0000000000005e857005db658b71@google.com>
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
next prev parent reply other threads:[~2023-02-02 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 1:34 [syzbot] INFO: task hung in rfcomm_process_sessions (2) syzbot
2023-02-02 4:55 ` syzbot [this message]
2023-02-02 14:01 ` Hillf Danton
[not found] <20220330102644.4510-1-hdanton@sina.com>
2022-03-30 11:54 ` syzbot
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=000000000000b09dc705f3b05f9b@google.com \
--to=syzbot+d761775dff24be3ad4be@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.