From: patchwork-bot+bluetooth@kernel.org
To: Yousef Alhouseen <alhouseenyousef@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
syzbot+fed5dce4553262f3b35c@syzkaller.appspotmail.com
Subject: Re: [PATCH] Bluetooth: bnep: pin L2CAP connection during netdev registration
Date: Tue, 30 Jun 2026 20:32:34 +0000 [thread overview]
Message-ID: <178285155488.267316.4327348213803627629.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260628005058.29072-1-alhouseenyousef@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 28 Jun 2026 02:50:58 +0200 you wrote:
> bnep_add_connection() reads the L2CAP connection without holding the
> channel lock, then passes its HCI device to register_netdev(). Controller
> teardown can clear and release that connection concurrently, leaving the
> network device registration path to dereference a freed parent device.
>
> Take a reference to the L2CAP connection while holding the channel lock.
> Retain it until register_netdev() has taken the parent device reference.
>
> [...]
Here is the summary with links:
- Bluetooth: bnep: pin L2CAP connection during netdev registration
https://git.kernel.org/bluetooth/bluetooth-next/c/d66f0661748e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-30 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 0:50 [PATCH] Bluetooth: bnep: pin L2CAP connection during netdev registration Yousef Alhouseen
2026-06-30 20:32 ` patchwork-bot+bluetooth [this message]
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=178285155488.267316.4327348213803627629.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alhouseenyousef@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+fed5dce4553262f3b35c@syzkaller.appspotmail.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