From: syzbot <syzbot+b69a625d06e8ece26415@syzkaller.appspotmail.com>
To: axboe@kernel.dk, 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, yangyingliang@huawei.com
Subject: Re: [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_exists
Date: Sun, 17 Nov 2024 06:03:03 -0800 [thread overview]
Message-ID: <6739f797.050a0220.87769.000f.GAE@google.com> (raw)
In-Reply-To: <0000000000006477b305f2b48b58@google.com>
syzbot suspects this issue was fixed by commit:
commit 08d1914293dae38350b8088980e59fbc699a72fe
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.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
next prev parent reply other threads:[~2024-11-17 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 16:28 [syzbot] possible deadlock in rfcomm_dlc_exists syzbot
2023-03-31 0:21 ` [syzbot] [bluetooth?] " syzbot
2024-11-17 14:03 ` syzbot [this message]
2024-12-24 14:09 ` [syzbot] Re: [syzbot] " syzbot
[not found] <20230331032008.3067-1-hdanton@sina.com>
2023-03-31 3:37 ` [syzbot] [bluetooth?] " syzbot
[not found] <20230331080108.3156-1-hdanton@sina.com>
2023-03-31 8:16 ` syzbot
[not found] <20230331084907.3220-1-hdanton@sina.com>
2023-03-31 9:18 ` 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=6739f797.050a0220.87769.000f.GAE@google.com \
--to=syzbot+b69a625d06e8ece26415@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--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=yangyingliang@huawei.com \
/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.