From: Kees Cook <keescook@chromium.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
keithpac@amazon.com, clang-built-linux@googlegroups.com,
linux-kbuild@vger.kernel.org, akpm@linux-foundation.org,
gregkh@linuxfoundation.org, dri-devel@lists.freedesktop.org,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-hardening@vger.kernel.org, gustavoars@kernel.org,
linux-staging@lists.linux.dev, linux-block@vger.kernel.org
Subject: Re: [PATCH 04/64] stddef: Introduce struct_group() helper macro
Date: Sat, 31 Jul 2021 08:10:20 -0700 [thread overview]
Message-ID: <202107310806.CD5D546DB7@keescook> (raw)
In-Reply-To: <CAKwiHFheDv2pwsm6Fa+-KnOFyvk7bfZQjb2BQ-CSwH61gxgVYg@mail.gmail.com>
On Sat, Jul 31, 2021 at 07:24:44AM +0200, Rasmus Villemoes wrote:
> On Sat, Jul 31, 2021, 04:59 Kees Cook <keescook@chromium.org> wrote:
>
> > On Fri, Jul 30, 2021 at 10:19:20PM +0000, Williams, Dan J wrote:
> > > On Wed, 2021-07-28 at 14:59 -0700, Kees Cook wrote:
> >
> > > /**
> > > * struct_group(NAME, MEMBERS)
> > > *
> > > @@ -67,7 +73,10 @@ enum {
> > > * @NAME: The name of the mirrored sub-struct
> > > * @MEMBERS: The member declarations for the mirrored structs
> > > */
> > > -#define struct_group(NAME, MEMBERS) \
> > > +#define struct_group(NAME, MEMBERS...) \
> > > struct_group_attr(NAME, /* no attrs */, MEMBERS)
> > >
> > > +#define struct_group_typed(TYPE, NAME, MEMBERS...) \
> > > + struct_group_attr_typed(TYPE, NAME, /* no attrs */, MEMBERS)
> > > +
> > > #endif
> >
> > Awesome! My instinct is to expose the resulting API as:
> >
> > __struct_group(type, name, attrs, members...)
> >
> > struct_group(name, members...)
> > struct_group_attr(name, attrs, members...)
> > struct_group_typed(type, name, members...)
>
> Bikeshed: can we use proper nomenclature please. s/type/tag/,
> s/typed/tagged.
Ah! Thank you. I went looking for the spec on what these are called and
couldn't find it. "struct $tag" is the type, then, yes? So IIUC now:
| type | members | name
| tag
struct foo { int bar; } baz;
--
Kees Cook
prev parent reply other threads:[~2021-07-31 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210727205855.411487-1-keescook@chromium.org>
[not found] ` <20210727205855.411487-5-keescook@chromium.org>
[not found] ` <41183a98-bdb9-4ad6-7eab-5a7292a6df84@rasmusvillemoes.dk>
[not found] ` <202107281456.1A3A5C18@keescook>
2021-07-30 22:19 ` [PATCH 04/64] stddef: Introduce struct_group() helper macro Williams, Dan J
2021-07-31 2:59 ` Kees Cook
[not found] ` <CAKwiHFheDv2pwsm6Fa+-KnOFyvk7bfZQjb2BQ-CSwH61gxgVYg@mail.gmail.com>
2021-07-31 15:10 ` Kees Cook [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=202107310806.CD5D546DB7@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dan.j.williams@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=keithpac@amazon.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=netdev@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