mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+b71bb48c13bf3fed3692@syzkaller.appspotmail.com>
To: ipravdin.official@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] possible deadlock in l2cap_conn_del
Date: Mon, 21 Jul 2025 15:35:02 -0700	[thread overview]
Message-ID: <687ec096.a70a0220.31ebea.071a.GAE@google.com> (raw)
In-Reply-To: <qqkqypzrbb3vyc2lm65byfbel2eblpobx6zqityolbzhy7y4za@mcovagqypg6l>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+b71bb48c13bf3fed3692@syzkaller.appspotmail.com
Tested-by: syzbot+b71bb48c13bf3fed3692@syzkaller.appspotmail.com

Tested on:

commit:         0ba71474 Bluetooth: hci_event: Mask data status from L..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=17af8fd4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2210d0e1e4249b81
dashboard link: https://syzkaller.appspot.com/bug?extid=b71bb48c13bf3fed3692
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2025-07-21 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <qqkqypzrbb3vyc2lm65byfbel2eblpobx6zqityolbzhy7y4za@mcovagqypg6l>
2025-07-21 22:35 ` syzbot [this message]
     [not found] <20250404011510.3744-1-hdanton@sina.com>
2025-04-04  1:44 ` syzbot
2025-03-31 19:16 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=687ec096.a70a0220.31ebea.071a.GAE@google.com \
    --to=syzbot+b71bb48c13bf3fed3692@syzkaller.appspotmail.com \
    --cc=ipravdin.official@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome