* [PATCH BlueZ v1] shared/rap: Fix step payload pointer in parse_step
@ 2026-06-23 11:11 Prathibha Madugonde
2026-06-24 19:31 ` patchwork-bot+bluetooth
0 siblings, 1 reply; 2+ messages in thread
From: Prathibha Madugonde @ 2026-06-23 11:11 UTC (permalink / raw)
To: linux-bluetooth; +Cc: luiz.dentz, quic_mohamull, quic_hbandi, quic_anubhavg
From: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
util_iov_pull advances iov_base before returning the new pointer, so
mode_iov.iov_base was set to the start of the *next* step's data.
Every step was therefore parsed using its successor's bytes.
Switch to util_iov_pull_mem which saves the original base, advances
iov, and returns the pre-advance pointer — correctly pointing to the
current step's payload.
---
src/shared/rap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/shared/rap.c b/src/shared/rap.c
index ecf7df5a7..dfb272d3a 100644
--- a/src/shared/rap.c
+++ b/src/shared/rap.c
@@ -2326,7 +2326,7 @@ static bool parse_step(struct bt_rap *rap, struct iovec *iov,
DBG(rap, " Step %u: mode=%u payload_len=%zu",
step_idx, step_mode, step_payload_len);
- payload = util_iov_pull(iov, step_payload_len);
+ payload = util_iov_pull_mem(iov, step_payload_len);
if (!payload) {
DBG(rap, "Insufficient data for step %u payload "
"(need %zu, have %zu)",
--
2.34.1
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH BlueZ v1] shared/rap: Fix step payload pointer in parse_step
2026-06-23 11:11 [PATCH BlueZ v1] shared/rap: Fix step payload pointer in parse_step Prathibha Madugonde
@ 2026-06-24 19:31 ` patchwork-bot+bluetooth
0 siblings, 0 replies; 2+ messages in thread
From: patchwork-bot+bluetooth @ 2026-06-24 19:31 UTC (permalink / raw)
To: Prathibha Madugonde
Cc: linux-bluetooth, luiz.dentz, quic_mohamull, quic_hbandi,
quic_anubhavg
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 23 Jun 2026 16:41:12 +0530 you wrote:
> From: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
>
> util_iov_pull advances iov_base before returning the new pointer, so
> mode_iov.iov_base was set to the start of the *next* step's data.
> Every step was therefore parsed using its successor's bytes.
>
> Switch to util_iov_pull_mem which saves the original base, advances
> iov, and returns the pre-advance pointer — correctly pointing to the
> current step's payload.
>
> [...]
Here is the summary with links:
- [BlueZ,v1] shared/rap: Fix step payload pointer in parse_step
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=40a58272a58f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-06-24 19:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-23 11:11 [PATCH BlueZ v1] shared/rap: Fix step payload pointer in parse_step Prathibha Madugonde
2026-06-24 19:31 ` patchwork-bot+bluetooth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox