Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	luiz.dentz@gmail.com, oss@fourdim.xyz, error27@gmail.com,
	elver@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/16] Bluetooth: L2CAP: fix and annotate l2cap_conn::chan_l locking
Date: Wed, 02 Sep 2026 21:30:07 +0000	[thread overview]
Message-ID: <178838460764.2957558.9167588069983760163.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1788013041.git.pav@iki.fi>

Hello:

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

On Sat, 29 Aug 2026 17:19:55 +0300 you wrote:
> The intent in current code is that:
> 
> - l2cap_conn::chan_l read/write is guarded by l2cap_conn::lock
> 
> - l2cap_chan_del called with held l2cap_chan::lock (l2cap_sock.c uses
>   this)
> 
> [...]

Here is the summary with links:
  - [01/16] Bluetooth: L2CAP: take chan->lock for l2cap_chan_add/ready/del
    (no matching commit)
  - [02/16] Bluetooth: L2CAP: add l2cap_chan_close_unlocked() and locking helpers
    (no matching commit)
  - [03/16] Bluetooth: L2CAP: fix race condition in l2cap_sock_shutdown()
    (no matching commit)
  - [04/16] Bluetooth: 6lowpan: use l2cap_chan_close_unlocked()
    (no matching commit)
  - [05/16] Bluetooth: L2CAP: remove unused l2cap_chan_close()
    (no matching commit)
  - [06/16] Bluetooth: 6lowpan: avoid concurrent peer_del() in bt_6lowpan_disconnect
    (no matching commit)
  - [07/16] Bluetooth: L2CAP: hold conn->lock for __l2cap_ecred_conn_rsp_defer
    (no matching commit)
  - [08/16] Bluetooth: L2CAP: hold l2cap_conn::lock in l2cap_connect_cfm()
    (no matching commit)
  - [09/16] Bluetooth: L2CAP: add annotations for l2cap_chan list locking
    (no matching commit)
  - [10/16] Bluetooth: L2CAP: take lock for l2cap_chan_del in l2cap_ecred_rsp_defer
    (no matching commit)
  - [11/16] Bluetooth: L2CAP: hold chan in l2cap_ecred_conn_rsp()
    (no matching commit)
  - [12/16] Bluetooth: L2CAP: annotate locking for l2cap_chan_del()
    https://git.kernel.org/bluetooth/bluetooth-next/c/6873eb51dcdd
  - [13/16] Bluetooth: L2CAP: annotate locking for l2cap_ops callbacks
    https://git.kernel.org/bluetooth/bluetooth-next/c/4149ba2a806c
  - [14/16] Bluetooth: L2CAP: make concurrent l2cap_set_timer() refcounting safe
    (no matching commit)
  - [15/16] Bluetooth: L2CAP: remove conditional locking from l2cap_connect()
    (no matching commit)
  - [16/16] Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn
    (no matching commit)

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



      parent reply	other threads:[~2026-09-02 21:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29 14:19 [PATCH 00/16] Bluetooth: L2CAP: fix and annotate l2cap_conn::chan_l locking Pauli Virtanen
2026-08-29 14:19 ` [PATCH 01/16] Bluetooth: L2CAP: take chan->lock for l2cap_chan_add/ready/del Pauli Virtanen
2026-08-29 15:45   ` Bluetooth: L2CAP: fix and annotate l2cap_conn::chan_l locking bluez.test.bot
2026-08-29 14:19 ` [PATCH 02/16] Bluetooth: L2CAP: add l2cap_chan_close_unlocked() and locking helpers Pauli Virtanen
2026-08-29 14:19 ` [PATCH 03/16] Bluetooth: L2CAP: fix race condition in l2cap_sock_shutdown() Pauli Virtanen
2026-08-29 14:19 ` [PATCH 04/16] Bluetooth: 6lowpan: use l2cap_chan_close_unlocked() Pauli Virtanen
2026-08-29 14:20 ` [PATCH 05/16] Bluetooth: L2CAP: remove unused l2cap_chan_close() Pauli Virtanen
2026-08-29 14:20 ` [PATCH 06/16] Bluetooth: 6lowpan: avoid concurrent peer_del() in bt_6lowpan_disconnect Pauli Virtanen
2026-08-29 14:20 ` [PATCH 07/16] Bluetooth: L2CAP: hold conn->lock for __l2cap_ecred_conn_rsp_defer Pauli Virtanen
2026-08-29 14:20 ` [PATCH 08/16] Bluetooth: L2CAP: hold l2cap_conn::lock in l2cap_connect_cfm() Pauli Virtanen
2026-08-29 14:20 ` [PATCH 09/16] Bluetooth: L2CAP: add annotations for l2cap_chan list locking Pauli Virtanen
2026-08-29 14:20 ` [PATCH 10/16] Bluetooth: L2CAP: take lock for l2cap_chan_del in l2cap_ecred_rsp_defer Pauli Virtanen
2026-08-29 14:20 ` [PATCH 11/16] Bluetooth: L2CAP: hold chan in l2cap_ecred_conn_rsp() Pauli Virtanen
2026-08-29 14:20 ` [PATCH 12/16] Bluetooth: L2CAP: annotate locking for l2cap_chan_del() Pauli Virtanen
2026-08-29 14:20 ` [PATCH 13/16] Bluetooth: L2CAP: annotate locking for l2cap_ops callbacks Pauli Virtanen
2026-08-29 14:20 ` [PATCH 14/16] Bluetooth: L2CAP: make concurrent l2cap_set_timer() refcounting safe Pauli Virtanen
2026-08-29 14:20 ` [PATCH 15/16] Bluetooth: L2CAP: remove conditional locking from l2cap_connect() Pauli Virtanen
2026-08-29 14:20 ` [PATCH 16/16] Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn Pauli Virtanen
2026-09-01 19:10 ` [PATCH 00/16] Bluetooth: L2CAP: fix and annotate l2cap_conn::chan_l locking patchwork-bot+bluetooth
2026-09-01 19:18   ` Luiz Augusto von Dentz
2026-09-02 21: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=178838460764.2957558.9167588069983760163.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=elver@google.com \
    --cc=error27@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=oss@fourdim.xyz \
    --cc=pav@iki.fi \
    /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