From: Gal Pressman <gal@nvidia.com>
To: Kees Cook <kees@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@kernel.org>,
Simon Horman <horms@kernel.org>,
linux-hardening@vger.kernel.org, Cosmin Ratiu <cratiu@nvidia.com>
Subject: Re: [PATCH net-next] net: Silence false field-spanning write warning in ip_tunnel_info_opts_set() memcpy
Date: Wed, 8 Jan 2025 08:56:00 +0200 [thread overview]
Message-ID: <7dae76b8-4b79-40dd-9aa5-050c44e060f0@nvidia.com> (raw)
In-Reply-To: <53D1D353-B8F6-4ADC-8F29-8C48A7C9C6F1@kernel.org>
On 08/01/2025 1:28, Kees Cook wrote:
>
>
> On January 7, 2025 8:55:09 AM PST, Gal Pressman <gal@nvidia.com> wrote:
>> When metadata_dst struct is allocated (using metadata_dst_alloc()), it
>> reserves room for options at the end of the struct.
>>
>> Similar to [1], change the memcpy() to unsafe_memcpy() as it is
>> guaranteed that enough room (md_size bytes) was allocated and the
>> field-spanning write is intentional.
>
> Why not just add an "options" flex array to struct ip_tunnel_info?
>
> E.g.:
>
> struct ip_tunnel_info {
> struct ip_tunnel_key key;
> struct ip_tunnel_encap encap;
> #ifdef CONFIG_DST_CACHE
> struct dst_cache dst_cache;
> #endif
> u8 options_len;
> u8 mode;
> u8 options[] __counted_by(options_len);
> };
>
>>
>> This resolves the following warning:
>> memcpy: detected field-spanning write (size 8) of single field "_Generic(info, const struct ip_tunnel_info * : ((const void *)((info) + 1)), struct ip_tunnel_info * : ((void *)((info) + 1)) )" at include/net/ip_tunnels.h:662 (size 0)
>
> Then you can drop this macro and just use: info->options
>
> Looks like you'd need to do it for all the types in struct metadata_dst, but at least you could stop hiding it from the compiler. :)
>
> -Kees
>
>
Thanks for the review Kees, I'll take a look into that.
next prev parent reply other threads:[~2025-01-08 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 16:55 [PATCH net-next] net: Silence false field-spanning write warning in ip_tunnel_info_opts_set() memcpy Gal Pressman
2025-01-07 23:28 ` Kees Cook
2025-01-08 6:56 ` Gal Pressman [this message]
2025-01-09 9:00 ` Gal Pressman
2025-01-09 16:52 ` Kees Cook
2025-01-12 6:37 ` Gal Pressman
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=7dae76b8-4b79-40dd-9aa5-050c44e060f0@nvidia.com \
--to=gal@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox