Linux bluetooth development
 help / color / mirror / Atom feed
From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com
Subject: Re: [PATCH 0/4] Bluetooth: L2CAP: part 2 of l2cap_conn::chan_l locking fixes
Date: Wed, 02 Sep 2026 00:48:31 +0300	[thread overview]
Message-ID: <82e061d0cb5d8a10ca6c745843843ed7bf1b1bea.camel@iki.fi> (raw)
In-Reply-To: <cover.1788296635.git.pav@iki.fi>

ke, 2026-09-02 kello 00:04 +0300, Pauli Virtanen kirjoitti:
> Rebase to fix conflict in remaining commits from series
> https://lore.kernel.org/linux-bluetooth/cover.1788013041.git.pav@iki.fi/
> 
> Fixed minor conflict vs. moved mutex_lock + l2cap_chan_lock in diff
> context
> commit ddaccd985bb0 ("Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect")
> 
> No other changes than resolving that.
> 
> Pauli Virtanen (4):
>   Bluetooth: L2CAP: take lock for l2cap_chan_del in
>     l2cap_ecred_rsp_defer
>   Bluetooth: L2CAP: annotate locking for l2cap_chan_del()
>   Bluetooth: L2CAP: annotate locking for l2cap_ops callbacks

Sashiko report comments that some callbacks in functions in l2cap_ops
are not marked with __must_hold(chan->lock) annotation.

That comment is not correct, e.g. l2cap_chan_send is called from
6lowpan.c and smp.c without holding chan->lock, so the annotations
cannot be added, it'd need solving locking issues first.

>   Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn
> 
>  include/net/bluetooth/l2cap.h |  65 +++++++++++--------
>  net/bluetooth/6lowpan.c       |   2 +
>  net/bluetooth/l2cap_core.c    | 113 ++++++++++++++++++++++++++++++++--
>  net/bluetooth/l2cap_sock.c    |   2 +
>  4 files changed, 150 insertions(+), 32 deletions(-)

-- 
Pauli Virtanen

  parent reply	other threads:[~2026-09-01 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 21:04 [PATCH 0/4] Bluetooth: L2CAP: part 2 of l2cap_conn::chan_l locking fixes Pauli Virtanen
2026-09-01 21:04 ` [PATCH 1/4] Bluetooth: L2CAP: take lock for l2cap_chan_del in l2cap_ecred_rsp_defer Pauli Virtanen
2026-09-01 22:38   ` Bluetooth: L2CAP: part 2 of l2cap_conn::chan_l locking fixes bluez.test.bot
2026-09-01 21:04 ` [PATCH 2/4] Bluetooth: L2CAP: annotate locking for l2cap_chan_del() Pauli Virtanen
2026-09-01 21:04 ` [PATCH 3/4] Bluetooth: L2CAP: annotate locking for l2cap_ops callbacks Pauli Virtanen
2026-09-01 21:04 ` [PATCH 4/4] Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn Pauli Virtanen
2026-09-01 21:48 ` Pauli Virtanen [this message]
2026-09-02 21:30 ` [PATCH 0/4] Bluetooth: L2CAP: part 2 of l2cap_conn::chan_l locking fixes patchwork-bot+bluetooth

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=82e061d0cb5d8a10ca6c745843843ed7bf1b1bea.camel@iki.fi \
    --to=pav@iki.fi \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    /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