From: Kees Cook <kees@kernel.org>
To: Coly Li <i@coly.li>
Cc: Coly Li <colyli@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Ard Biesheuvel <ardb@kernel.org>,
linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] md/bcache: Mark __nonstring look-up table
Date: Thu, 8 May 2025 08:58:48 -0700 [thread overview]
Message-ID: <202505080844.DD7F50F0A@keescook> (raw)
In-Reply-To: <851B250D-A22C-4B47-BBAC-55284B5B5790@coly.li>
On Thu, May 08, 2025 at 11:01:34AM +0800, Coly Li wrote:
>
> > 2025年4月19日 11:55,Coly Li <i@coly.li> 写道:
> >
> >
> >
> >> 2025年4月19日 04:21,Kees Cook <kees@kernel.org> 写道:
> >>
> >> GCC 15's new -Wunterminated-string-initialization notices that the 16
> >> character lookup table "zero_uuid" (which is not used as a C-String)
> >> needs to be marked as "nonstring":
> >>
> >> drivers/md/bcache/super.c: In function 'uuid_find_empty':
> >> drivers/md/bcache/super.c:549:43: warning: initializer-string for array of 'char' truncates NUL terminator but destination lacks 'nonstring' attribute (17 chars into 16 available) [-Wunterminated-string-initialization]
> >> 549 | static const char zero_uuid[16] = "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0";
> >> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>
> >> Add the annotation (since it is not used as a C-String), and switch the
> >> initializer to an array of bytes.
> >>
> >> Signed-off-by: Kees Cook <kees@kernel.org>
> >> ---
> >> v2: use byte array initializer (colyli)
> >> v1: https://lore.kernel.org/all/20250416220135.work.394-kees@kernel.org/
> >> Cc: Coly Li <colyli@kernel.org>
> >> Cc: Kent Overstreet <kent.overstreet@linux.dev>
> >> Cc: Ard Biesheuvel <ardb@kernel.org>
> >> Cc: linux-bcache@vger.kernel.org
> >> ---
> >> drivers/md/bcache/super.c | 3 ++-
> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
> >> index e42f1400cea9..a76ce92502ed 100644
> >> --- a/drivers/md/bcache/super.c
> >> +++ b/drivers/md/bcache/super.c
> >> @@ -546,7 +546,8 @@ static struct uuid_entry *uuid_find(struct cache_set *c, const char *uuid)
> >>
> >> static struct uuid_entry *uuid_find_empty(struct cache_set *c)
> >> {
> >> - static const char zero_uuid[16] = "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0";
> >> + static const char zero_uuid[] __nonstring =
> >
>
> Hi Kees,
>
> > I notice zero_uuid[16] changes to zero_uuid[], then the element number information is removed.
> >
> > Is it OK for GCC 15 to only add __nonstring and keep zero_uuid[16]?
Either way is fine. I can update the patch to use the "[16]" again if
you'd like?
-Kees
> Ping ?
>
> You are expert here, I need your opinion.
>
> Thanks.
>
> Coly Li
>
>
>
> >> + { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 };
> >>
> >> return uuid_find(c, zero_uuid);
> >> }
> >> --
> >> 2.34.1
>
>
--
Kees Cook
next prev parent reply other threads:[~2025-05-08 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 20:21 [PATCH v2] md/bcache: Mark __nonstring look-up table Kees Cook
2025-04-19 3:55 ` Coly Li
2025-05-08 3:01 ` Coly Li
2025-05-08 15:58 ` Kees Cook [this message]
2025-05-08 15:59 ` Coly Li
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=202505080844.DD7F50F0A@keescook \
--to=kees@kernel.org \
--cc=ardb@kernel.org \
--cc=colyli@kernel.org \
--cc=i@coly.li \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@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 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.