From: patchwork-bot+bluetooth@kernel.org
To: Maiquel Paiva <maiquelpaiva@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
gregkh@linuxfoundation.org, marcel@holtmann.org,
stable@vger.kernel.org
Subject: Re: [PATCH v9] Bluetooth: mgmt: Fix race condition in mesh handling
Date: Tue, 17 Feb 2026 18:50:11 +0000 [thread overview]
Message-ID: <177135421132.600961.11662077069092767066.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260214130610.68236-1-maiquelpaiva@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 14 Feb 2026 13:06:10 +0000 you wrote:
> This patch addresses race conditions in mesh handling within mgmt_util.c.
>
> The functions mgmt_mesh_add and mgmt_mesh_find modify or traverse the
> mesh_pending list without locking. This patch uses guard(mutex) with
> the existing mgmt_pending_lock to protect the critical sections, as
> suggested by maintainers in previous reviews.
>
> [...]
Here is the summary with links:
- [v9] Bluetooth: mgmt: Fix race condition in mesh handling
https://git.kernel.org/bluetooth/bluetooth-next/c/003ca042a386
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-02-17 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 13:06 [PATCH v9] Bluetooth: mgmt: Fix race condition in mesh handling Maiquel Paiva
2026-02-14 14:02 ` [v9] " bluez.test.bot
2026-02-17 18:50 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-14 14:56 [PATCH v9] " Maiquel Paiva
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=177135421132.600961.11662077069092767066.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=maiquelpaiva@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.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