All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/4] gatt-server: Check prepare write length before reallocating
Date: Thu, 17 Sep 2026 17:30:04 +0000	[thread overview]
Message-ID: <178966620463.3782583.6861381345742673420.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910184216.1601639-1-luiz.dentz@gmail.com>

Hello:

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

On Thu, 10 Sep 2026 14:42:13 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> append_prep_data() grew the buffer and copied the new fragment into it
> before rejecting a total length above UINT16_MAX. On overflow the
> allocation had already been enlarged and written while prep_data->length
> was left at its previous value, desynchronising the buffer from its
> tracked size.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/4] gatt-server: Check prepare write length before reallocating
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=985ee7b3ab0e
  - [BlueZ,v1,2/4] adapter: Unify the A2DP admin allowlist UUID mapping
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0ccdf019681c
  - [BlueZ,v1,3/4] battery: Document the unknown sentinels and fix a stale name
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2ffbcf6f9d38
  - [BlueZ,v1,4/4] client/bluetoothctl: Declare the controller helper in its own header
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e5dc89d28253

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-17 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 18:42 [PATCH BlueZ v1 1/4] gatt-server: Check prepare write length before reallocating Luiz Augusto von Dentz
2026-09-10 18:42 ` [PATCH BlueZ v1 2/4] adapter: Unify the A2DP admin allowlist UUID mapping Luiz Augusto von Dentz
2026-09-10 18:42 ` [PATCH BlueZ v1 3/4] battery: Document the unknown sentinels and fix a stale name Luiz Augusto von Dentz
2026-09-10 18:42 ` [PATCH BlueZ v1 4/4] client/bluetoothctl: Declare the controller helper in its own header Luiz Augusto von Dentz
2026-09-10 20:06 ` [BlueZ,v1,1/4] gatt-server: Check prepare write length before reallocating bluez.test.bot
2026-09-17 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=178966620463.3782583.6861381345742673420.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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.