mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Use RCU-safe device list removal
Date: Wed, 07 Oct 2026 17:30:06 +0000	[thread overview]
Message-ID: <179139420653.3628206.2096536706982565327.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0231-v5-32295fa35099b0d50b92@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue,  6 Oct 2026 15:35:23 +0800 you wrote:
> RCU readers of bt_6lowpan_devices must be able to follow an adapter's
> forward link until their read-side critical section ends. The entries
> are published with list_add_rcu(), but device_event() removes an entry
> on NETDEV_UNREGISTER with list_del(), poisoning that link.
> 
> When an adapter is being unregistered and 6LoWPAN is enabled, a
> 6lowpan_control debugfs write with an existing LE L2CAP connection can
> enter lookup_peer() after unregister's first synchronize_net(). If the
> connection has no peer on that adapter, the reader must advance to the
> next list entry. Neither RTNL nor devices_lock excludes this RCU reader.
> 
> [...]

Here is the summary with links:
  - Bluetooth: 6LoWPAN: Use RCU-safe device list removal
    https://git.kernel.org/bluetooth/bluetooth-next/c/fabf38c7e07f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-10-07 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06  7:35 Cen Zhang
2026-10-07 17:30 ` 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=179139420653.3628206.2096536706982565327.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®