From: sashiko-bot@kernel.org
To: "Alejandro Colomar" <alx@kernel.org>
Cc: devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 2/6] string: Warn if the prefix is the empty string
Date: Wed, 11 Nov 2026 20:15:04 +0000 [thread overview]
Message-ID: <sashiko-outbox-209624@kernel.org> (raw)
In-Reply-To: <cd09427148a0c4718b46029c9e806f9dc1622f9b.1794425425.git.alx@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] string: missing linux/bug.h include for WARN_ON_ONCE() in
str_has_prefix()
--
commit 544547ef558a49b7dbb876a077fff7f7bedc8b0c
Author: Alejandro Colomar <alx@kernel.org>
string: Warn if the prefix is the empty string
This commit adds a WARN_ON_ONCE() check to str_has_prefix() and documents
that passing an empty prefix string is unsupported.
Link: https://lore.kernel.org/linux-hardening/20261104-fwnode-for-each-prop-v1-1-6e28fe1c72c4@oss.qualcomm.com/
> diff --git a/include/linux/string.h b/include/linux/string.h
> index ec6ca50599fed..8e6b78c6196a7 100644
> --- a/include/linux/string.h
> +++ b/include/linux/string.h
> @@ -561,6 +561,10 @@ static inline char *strprefix(const char *s, const char *prefix)
> * This is similar to strprefix(), but returns an offset instead of
> * a pointer.
> *
> + * Unlike for strprefix(), if the prefix is an empty string, the
> + * behavior is undefined. If you need to support arbitrary prefixes,
> + * use strprefix().
> + *
> * Returns:
> * * strlen(@prefix) if @str starts with @prefix
> * * 0 if @str does not start with @prefix
> @@ -568,6 +572,7 @@ static inline char *strprefix(const char *s, const char *prefix)
> static __always_inline size_t str_has_prefix(const char *str, const char *prefix)
> {
> size_t len = strlen(prefix);
> + WARN_ON_ONCE(len == 0);
[Severity: High]
Does include/linux/string.h need to include linux/bug.h for WARN_ON_ONCE()?
Currently, include/linux/string.h only pulls in linux/bug.h transitively
through linux/fortify-string.h when CONFIG_FORTIFY_SOURCE is enabled and
__NO_FORTIFY is not defined. Because str_has_prefix() is an inline function
rather than a macro, translation units that include linux/string.h without
linux/bug.h (such as arch/x86/lib/string_32.c with __NO_FORTIFY, or
lib/net_utils.c when CONFIG_FORTIFY_SOURCE is disabled) fail to build with
an implicit declaration of WARN_ON_ONCE().
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794425425.git.alx@kernel.org?part=2
next prev parent reply other threads:[~2026-11-11 20:15 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:12 [PATCH v1 0/2] Add strprefix() and fix a bug with it Alejandro Colomar
2026-11-05 11:21 ` Alejandro Colomar
2026-11-05 11:13 ` [PATCH v1 1/2] string: Add strprefix(), and deprecate str_has_prefix() Alejandro Colomar
2026-11-05 11:27 ` Andy Shevchenko
2026-11-05 12:28 ` Alejandro Colomar
2026-11-05 16:14 ` Steven Rostedt
2026-11-05 16:33 ` Alejandro Colomar
2026-11-05 16:50 ` Steven Rostedt
2026-11-05 17:46 ` Alejandro Colomar
2026-11-05 18:08 ` Andy Shevchenko
2026-11-05 18:12 ` Andy Shevchenko
2026-11-05 21:24 ` Alejandro Colomar
2026-11-05 21:48 ` Linus Torvalds
2026-11-05 22:25 ` Alejandro Colomar
2026-11-05 23:21 ` Linus Torvalds
2026-11-06 0:01 ` Alejandro Colomar
2026-11-06 7:15 ` Krzysztof Kozlowski
2026-11-05 11:13 ` [PATCH v1 2/2] device property: Fix fwnode_name_eq() for empty node names Alejandro Colomar
2026-11-05 11:24 ` [PATCH v1 0/2] Add strprefix() and fix a bug with it Andy Shevchenko
2026-11-05 11:38 ` Alejandro Colomar
2026-11-05 11:59 ` Andy Shevchenko
2026-11-05 12:30 ` Bartosz Golaszewski
2026-11-05 12:49 ` Alejandro Colomar
2026-11-05 12:46 ` [PATCH v2 " Alejandro Colomar
2026-11-05 12:46 ` [PATCH v2 1/2] string: Add strprefix(), and deprecate str_has_prefix() Alejandro Colomar
2026-11-05 12:51 ` Geert Uytterhoeven
2026-11-05 13:12 ` Alejandro Colomar
2026-11-07 2:44 ` Maciej W. Rozycki
2026-11-07 7:33 ` Alejandro Colomar
2026-11-08 11:05 ` Maciej W. Rozycki
2026-11-08 11:49 ` Alejandro Colomar
2026-11-08 11:54 ` Alejandro Colomar
2026-11-09 22:36 ` Andy Shevchenko
2026-11-05 12:46 ` [PATCH v2 2/2] device property: Fix fwnode_name_eq() for empty node names Alejandro Colomar
2026-11-05 14:01 ` [PATCH v2 0/2] Add strprefix() and fix a bug with it Bartosz Golaszewski
2026-11-05 14:16 ` Alejandro Colomar
2026-11-05 14:42 ` Andy Shevchenko
2026-11-05 15:06 ` Alejandro Colomar
2026-11-07 2:42 ` Maciej W. Rozycki
2026-11-07 14:05 ` Andy Shevchenko
2026-11-05 15:00 ` Bartosz Golaszewski
2026-11-05 15:14 ` Alejandro Colomar
2026-11-05 15:21 ` Krzysztof Kozlowski
2026-11-05 16:27 ` Steven Rostedt
2026-11-05 16:30 ` Krzysztof Kozlowski
2026-11-05 16:42 ` Alejandro Colomar
2026-11-11 19:55 ` [PATCH v4 0/6] " Alejandro Colomar
2026-11-11 19:55 ` [PATCH v4 1/6] string: Add strprefix(), and deprecate str_has_prefix() Alejandro Colomar
2026-11-11 20:14 ` sashiko-bot
2026-11-12 22:31 ` David Laight
2026-11-12 23:34 ` Alejandro Colomar
2026-11-11 19:55 ` [PATCH v4 2/6] string: Warn if the prefix is the empty string Alejandro Colomar
2026-11-11 20:15 ` sashiko-bot [this message]
2026-11-12 1:17 ` kernel test robot
2026-11-12 1:28 ` kernel test robot
2026-11-11 19:55 ` [PATCH v4 3/6] device property: Fix fwnode_name_eq() for empty node names Alejandro Colomar
2026-11-11 19:55 ` [PATCH v4 4/6] stddef: Add const_cast() Alejandro Colomar
2026-11-11 20:11 ` sashiko-bot
2026-11-11 20:18 ` Alejandro Colomar
2026-11-11 19:55 ` [PATCH v4 5/6] string: Add [C]QChar_of() and QVoid_of() Alejandro Colomar
2026-11-11 19:55 ` [PATCH v4 6/6] string: Make strprefix() const-qualifier-generic Alejandro Colomar
2026-11-11 20:11 ` sashiko-bot
2026-11-11 19:57 ` [PATCH v4 0/6] Add strprefix() and fix a bug with it Alejandro Colomar
2026-11-12 15:17 ` Andy Shevchenko
2026-11-11 20:07 ` Alejandro Colomar
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=sashiko-outbox-209624@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alx@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.