From: patchwork-bot+netdevbpf@kernel.org
To: Nandor Kracser <nandor@riptides.io>
Cc: netdev@vger.kernel.org, john.fastabend@gmail.com,
kuba@kernel.org, sd@queasysnail.net, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] tls: avoid field-spanning write when copying crypto info
Date: Fri, 23 Oct 2026 23:10:06 +0000 [thread overview]
Message-ID: <179279700631.1316845.12189047756278316943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261021073233.16720-1-nandor@riptides.io>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Oct 2026 09:32:33 +0200 you wrote:
> do_tls_setsockopt_conf() copies the cipher-specific part of the crypto
> info to crypto_info + 1, where crypto_info points at the 4-byte info
> member of union tls_crypto_context. When optval is a kernel sockptr,
> copy_from_sockptr_offset() is a memcpy(), and FORTIFY_SOURCE bounds the
> destination by that member:
>
> [ 6.948348] memcpy: detected field-spanning write (size 52) of single field "dst" at include/linux/sockptr.h:49 (size 0)
> [ 6.948480] WARNING: include/linux/sockptr.h:49 at tls_setsockopt+0x9b2/0xa30, CPU#1: init/1
> [ 7.001355] Call Trace:
> [ 7.003146] do_sock_setsockopt+0xb0/0x190
> [ 7.003975] __sys_setsockopt+0x76/0xc0
> [ 7.005368] do_syscall_64+0xda/0x4b0
>
> [...]
Here is the summary with links:
- [net] tls: avoid field-spanning write when copying crypto info
https://git.kernel.org/netdev/net/c/c43c1c24f3cd
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-10-23 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 7:32 Nandor Kracser
2026-10-23 23:10 ` patchwork-bot+netdevbpf [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=179279700631.1316845.12189047756278316943.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nandor@riptides.io \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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
all inboxes | Powered by JetHome®