From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Kees Cook <kees@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, <cferris@google.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, <netdev@vger.kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-hardening@vger.kernel.org>
Subject: Re: [PATCH] UAPI: net/sched: Open-code __struct_group() in flex struct tc_u32_sel
Date: Tue, 17 Dec 2024 15:55:41 +0100 [thread overview]
Message-ID: <f4947447-aa66-470c-a48d-06ed77be58da@intel.com> (raw)
In-Reply-To: <20241217025950.work.601-kees@kernel.org>
From: Kees Cook <kees@kernel.org>
Date: Mon, 16 Dec 2024 18:59:55 -0800
> This switches to using a manually constructed form of struct tagging
> to avoid issues with C++ being unable to parse tagged structs within
> anonymous unions, even under 'extern "C"':
>
> ../linux/include/uapi/linux/pkt_cls.h:25124: error: ‘struct tc_u32_sel::<unnamed union>::tc_u32_sel_hdr,’ invalid; an anonymous union may only have public non-static data members [-fpermissive]
I worked around that like this in the past: [0]
As I'm not sure it would be fine to fix every such occurrence manually
by open-coding.
What do you think?
>
> To avoid having multiple struct member lists, use a define to declare
> them.
>
> Reported-by: cferris@google.com
> Closes: https://lore.kernel.org/linux-hardening/Z1HZpe3WE5As8UAz@google.com/
> Fixes: 216203bdc228 ("UAPI: net/sched: Use __struct_group() in flex struct tc_u32_sel")
> Link: https://lore.kernel.org/r/202412120927.943DFEDD@keescook
> Signed-off-by: Kees Cook <kees@kernel.org>
> ---
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Jamal Hadi Salim <jhs@mojatatu.com>
> Cc: Cong Wang <xiyou.wangcong@gmail.com>
> Cc: Jiri Pirko <jiri@resnulli.us>
> Cc: netdev@vger.kernel.org
> ---
> include/uapi/linux/pkt_cls.h | 34 +++++++++++++++++++++-------------
> 1 file changed, 21 insertions(+), 13 deletions(-)
>
> diff --git a/include/uapi/linux/pkt_cls.h b/include/uapi/linux/pkt_cls.h
> index 2c32080416b5..02aee6ed6bf0 100644
> --- a/include/uapi/linux/pkt_cls.h
> +++ b/include/uapi/linux/pkt_cls.h
> @@ -245,20 +245,28 @@ struct tc_u32_key {
> int offmask;
> };
>
> +#define tc_u32_sel_hdr_members \
> + unsigned char flags; \
> + unsigned char offshift; \
> + unsigned char nkeys; \
> + __be16 offmask; \
> + __u16 off; \
> + short offoff; \
> + short hoff; \
> + __be32 hmask
> +
> +struct tc_u32_sel_hdr {
> + tc_u32_sel_hdr_members;
> +};
> +
> struct tc_u32_sel {
> - /* New members MUST be added within the __struct_group() macro below. */
> - __struct_group(tc_u32_sel_hdr, hdr, /* no attrs */,
> - unsigned char flags;
> - unsigned char offshift;
> - unsigned char nkeys;
> -
> - __be16 offmask;
> - __u16 off;
> - short offoff;
> -
> - short hoff;
> - __be32 hmask;
> - );
> + /* Open-coded struct_group() to avoid C++ errors. */
> + union {
> + struct tc_u32_sel_hdr hdr;
> + struct {
> + tc_u32_sel_hdr_members;
> + };
> + };
> struct tc_u32_key keys[];
> };
[0]
https://github.com/alobakin/linux/commit/2a065c7bae821f5fa85fff6f97fbbd460f4aa0f3
Thanks,
Olek
next prev parent reply other threads:[~2024-12-17 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 2:59 [PATCH] UAPI: net/sched: Open-code __struct_group() in flex struct tc_u32_sel Kees Cook
2024-12-17 14:55 ` Alexander Lobakin [this message]
2024-12-17 15:58 ` Gustavo A. R. Silva
2024-12-17 16:04 ` Alexander Lobakin
2024-12-17 16:25 ` Gustavo A. R. Silva
2024-12-17 16:54 ` Alexander Lobakin
2024-12-17 18:30 ` Gustavo A. R. Silva
[not found] ` <CANtHk4nhH9XJi5+9BAu3kFoL14+4YAZTH7t6QApEvEAeMxdXgw@mail.gmail.com>
2024-12-17 19:19 ` Gustavo A. R. Silva
2024-12-17 20:25 ` Kees Cook
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=f4947447-aa66-470c-a48d-06ed77be58da@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=cferris@google.com \
--cc=gustavoars@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.