From: Kees Cook <keescook@chromium.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andy Shevchenko <andy@kernel.org>,
Justin Stitt <justinstitt@google.com>,
linux-hardening@vger.kernel.org,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowang@redhat.com>,
kernel test robot <lkp@intel.com>,
Nathan Chancellor <nathan@kernel.org>,
Azeem Shaikh <azeemshaikh38@gmail.com>,
linux-kernel@vger.kernel.org, linux-um@lists.infradead.org
Subject: Re: [PATCH v2 2/4] string: Allow 2-argument strscpy()
Date: Mon, 5 Feb 2024 05:01:49 -0800 [thread overview]
Message-ID: <202402050459.892907C59C@keescook> (raw)
In-Reply-To: <CAMuHMdU2c75WDCX+ptQgB7h0taHjG2pwL9db6gE3LKxv5Vz04Q@mail.gmail.com>
On Mon, Feb 05, 2024 at 01:47:08PM +0100, Geert Uytterhoeven wrote:
> > +/*
> > + * The 2 argument style can only be used when dst is an array with a
> > + * known size.
> > + */
> > +#define __strscpy0(dst, src, ...) \
> > + sized_strscpy(dst, src, sizeof(dst) + __must_be_array(dst))
> > +#define __strscpy1(dst, src, size) sized_strscpy(dst, src, size)
>
> (dst), (src), (size) etc.
I normally don't do this when macro args are being expanded into
function arguments. I've only done it for when macro args are used in
expressions. Am I missing a side-effect here, or is this more about
stylistic consistency?
--
Kees Cook
next prev parent reply other threads:[~2024-02-05 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 12:35 [PATCH v2 0/4] string: Allow 2-argument strscpy() Kees Cook
2024-02-05 12:35 ` [PATCH v2 1/4] string: Redefine strscpy_pad() as a macro Kees Cook
2024-02-05 12:35 ` [PATCH v2 2/4] string: Allow 2-argument strscpy() Kees Cook
2024-02-05 12:47 ` Geert Uytterhoeven
2024-02-05 12:58 ` Andy Shevchenko
2024-02-05 13:01 ` Kees Cook [this message]
2024-02-05 13:07 ` Geert Uytterhoeven
2024-02-05 12:35 ` [PATCH v2 3/4] string: Allow 2-argument strscpy_pad() Kees Cook
2024-02-05 12:48 ` Geert Uytterhoeven
2024-02-05 12:57 ` Andy Shevchenko
2024-02-05 12:35 ` [PATCH v2 4/4] um: Convert strscpy() usage to 2-argument style Kees Cook
2024-02-05 12:50 ` Geert Uytterhoeven
2024-02-05 12:57 ` Andy Shevchenko
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=202402050459.892907C59C@keescook \
--to=keescook@chromium.org \
--cc=andy@kernel.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=azeemshaikh38@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jasowang@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=justinstitt@google.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=richard@nod.at \
--cc=willemdebruijn.kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox