From: patchwork-bot+bluetooth@kernel.org
To: Bart Philips <bartphilips1@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, bart.philips@inspiro.nl
Subject: Re: [PATCH BlueZ 0/1] fix writes to attributes of size 512
Date: Thu, 10 Aug 2023 00:10:23 +0000 [thread overview]
Message-ID: <169162622371.3909.9864804498327871801.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230809202724.15429-1-bart.philips@inspiro.nl>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 9 Aug 2023 22:27:22 +0200 you wrote:
> writing attributes of length 512 fails, although the Bluetooth spec (Vol 4, Part F, 3.2.9) states that attributes sizes up to 512 are allowed. The check_length calls in write_cb and prep_write_cb in gatt-server.c currently pass the length parameter that include the handle/offset length and therefore fail for attributes of length 512. This patch subtracts the handle/offset length before passing it to the check_length function, allowing writes to attributes up to 512 in size.
>
> Bart Philips (1):
> fix writing attributes of length 512
>
> src/shared/gatt-server.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Here is the summary with links:
- [BlueZ,1/1] fix writing attributes of length 512
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8bf3a4a265bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-10 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 20:27 [PATCH BlueZ 0/1] fix writes to attributes of size 512 Bart Philips
2023-08-09 20:27 ` [PATCH BlueZ 1/1] fix writing attributes of length 512 Bart Philips
2023-08-09 23:00 ` fix writes to attributes of size 512 bluez.test.bot
2023-08-10 0:10 ` 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=169162622371.3909.9864804498327871801.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bart.philips@inspiro.nl \
--cc=bartphilips1@gmail.com \
--cc=linux-bluetooth@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