From: Kees Cook <kees@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Kees Cook <kees@kernel.org>, Miguel Ojeda <ojeda@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
kernel test robot <lkp@intel.com>,
Andy Shevchenko <andy@kernel.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Philipp Reisner <philipp.reisner@linbit.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
llvm@lists.linux.dev
Subject: [PATCH v2 0/3] string.h: Use ARRAY_SIZE() for memtostr*()/strtomem*()
Date: Thu, 6 Feb 2025 13:40:05 -0800 [thread overview]
Message-ID: <20250206213532.it.087-kees@kernel.org> (raw)
Work around a Clang <15 bug by switching to ARRAY_SIZE() (with the
added benefit of explicitly checking for char array arguments) in
memtostr*/strtomem*().
v2:
- change __must_be_byte_array to __must_be_byte_array() (david)
- add missed Suggested-by (kent)
- clarify move log (miguel)
- clarify cover letter Clang version (andy)
v1: https://lore.kernel.org/lkml/20250206175216.work.225-kees@kernel.org/
-Kees
Kees Cook (3):
compiler.h: Move C string helpers into C-only kernel section
compiler.h: Introduce __must_be_byte_array()
string.h: Use ARRAY_SIZE() for memtostr*()/strtomem*()
include/linux/compiler.h | 32 +++++++++++++++++++-------------
include/linux/string.h | 12 ++++++++----
2 files changed, 27 insertions(+), 17 deletions(-)
--
2.34.1
next reply other threads:[~2025-02-06 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 21:40 Kees Cook [this message]
2025-02-06 21:40 ` [PATCH v2 1/3] compiler.h: Move C string helpers into C-only kernel section Kees Cook
2025-02-06 21:40 ` [PATCH v2 2/3] compiler.h: Introduce __must_be_byte_array() Kees Cook
2025-02-06 21:40 ` [PATCH v2 3/3] string.h: Use ARRAY_SIZE() for memtostr*()/strtomem*() Kees Cook
2025-02-06 23:59 ` Suren Baghdasaryan
2025-02-07 1:01 ` 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=20250206213532.it.087-kees@kernel.org \
--to=kees@kernel.org \
--cc=andy@kernel.org \
--cc=justinstitt@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=luc.vanoostenryck@gmail.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=philipp.reisner@linbit.com \
--cc=surenb@google.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.