From: Kees Cook <kees@kernel.org>
To: Andy Shevchenko <andy@kernel.org>, Kees Cook <kees@kernel.org>
Cc: Justin Stitt <justinstitt@google.com>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Miguel Ojeda <ojeda@kernel.org>, Marco Elver <elver@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Hao Luo <haoluo@google.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
linux-sparse@vger.kernel.org, linux-hardening@vger.kernel.org,
Bill Wendling <morbo@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Jakub Kicinski <kuba@kernel.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Tony Ambardar <tony.ambardar@gmail.com>,
Petr Pavlu <petr.pavlu@suse.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] string: Check for "nonstring" attribute on strscpy() arguments
Date: Thu, 22 Aug 2024 17:05:22 -0700 [thread overview]
Message-ID: <172437152070.4121900.7735546714762971895.b4-ty@kernel.org> (raw)
In-Reply-To: <20240805214340.work.339-kees@kernel.org>
On Mon, 05 Aug 2024 14:43:44 -0700, Kees Cook wrote:
> GCC already checks for arguments that are marked with the "nonstring"[1]
> attribute when used on standard C String API functions (e.g. strcpy). Gain
> this compile-time checking also for the kernel's primary string copying
> function, strscpy().
>
> Note that Clang has neither "nonstring" nor __builtin_has_attribute().
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] string: Check for "nonstring" attribute on strscpy() arguments
https://git.kernel.org/kees/c/559048d156ff
Take care,
--
Kees Cook
prev parent reply other threads:[~2024-08-23 0:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 21:43 [PATCH] string: Check for "nonstring" attribute on strscpy() arguments Kees Cook
2024-08-06 10:29 ` Przemek Kitszel
2024-08-23 0:04 ` Kees Cook
2024-08-06 10:46 ` Miguel Ojeda
2024-08-23 0:05 ` 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=172437152070.4121900.7735546714762971895.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andy@kernel.org \
--cc=elver@google.com \
--cc=haoluo@google.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luc.vanoostenryck@gmail.com \
--cc=mark.rutland@arm.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tony.ambardar@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