From: patchwork-bot+bluetooth@kernel.org
To: Cen Zhang <zzzccc427@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, jjzuming@gmail.com
Subject: Re: [PATCH] Bluetooth: 6lowpan: Drain RCU readers on registration failure
Date: Fri, 09 Oct 2026 14:20:07 +0000 [thread overview]
Message-ID: <179155560751.812174.8668330528853448667.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0230-v4-fd2c82b141a5bc3c5841@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 8 Oct 2026 12:11:35 +0800 you wrote:
> A lowpan_btle_dev is embedded in its net_device allocation and must
> remain alive until readers of bt_6lowpan_devices have left their RCU
> sections. setup_netdev() publishes it before registration, but its
> error path only unlinks it before calling free_netdev().
>
> If a second controller's registration fails while multicast is sent
> on an existing 6LoWPAN interface, send_mcast_pkt() can already have
> selected the new entry. It reads entry->netdev before checking which
> interface owns it. An early failure, such as allocating the device's
> name node, leaves NETREG_UNINITIALIZED, so free_netdev() releases the
> storage immediately.
>
> [...]
Here is the summary with links:
- Bluetooth: 6lowpan: Drain RCU readers on registration failure
https://git.kernel.org/bluetooth/bluetooth-next/c/f664d75735b0
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-10-09 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 4:11 [PATCH] Bluetooth: 6lowpan: Drain RCU readers on registration failure Cen Zhang
2026-10-08 8:08 ` bluez.test.bot
2026-10-09 14:20 ` 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=179155560751.812174.8668330528853448667.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=jjzuming@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=zzzccc427@gmail.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.