From: patchwork-bot+bluetooth@kernel.org
To: Ali Ahmet Memis <ali@iusegentoo.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org, pav@iki.fi,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: ISO: zero the sockaddr before returning it in getname
Date: Fri, 07 Aug 2026 16:30:17 +0000 [thread overview]
Message-ID: <178612021790.1887768.1776053981475041255.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806230621.10105-1-ali@iusegentoo.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 6 Aug 2026 23:06:21 +0000 you wrote:
> iso_sock_getname() fills a struct sockaddr_iso in place and returns its
> size without clearing it first, so bytes it does not write are copied to
> user space from the kernel stack. The getsockname(2) and getpeername(2)
> paths both run through do_getsockname(), which hands getname() an
> uninitialized sockaddr_storage on the stack and copies back up to the
> number of bytes getname() returns, so the driver has to initialize every
> byte it accounts for.
>
> [...]
Here is the summary with links:
- Bluetooth: ISO: zero the sockaddr before returning it in getname
https://git.kernel.org/bluetooth/bluetooth-next/c/e25de80035a3
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:[~2026-08-07 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 23:06 [PATCH] Bluetooth: ISO: zero the sockaddr before returning it in getname Ali Ahmet Memis
2026-08-07 1:14 ` bluez.test.bot
2026-08-07 16: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=178612021790.1887768.1776053981475041255.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=ali@iusegentoo.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pav@iki.fi \
--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