From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v3] target/s390x/arch_dump: Fix warning for the name field in the PT_NOTE section
Date: Mon, 8 Feb 2021 12:31:44 +0100 [thread overview]
Message-ID: <20210208123144.68f6144d.cohuck@redhat.com> (raw)
In-Reply-To: <20210205093921.848260-1-thuth@redhat.com>
On Fri, 5 Feb 2021 10:39:21 +0100
Thomas Huth <thuth@redhat.com> wrote:
> There is a compiler warning with GCC 9.3 when compiling with
> the -fsanitize=thread compiler flag:
>
> In function 'strncpy',
> inlined from 's390x_write_elf64_notes' at ../target/s390x/arch_dump.c:219:9:
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error:
> '__builtin_strncpy' specified bound 8 equals destination size
> [-Werror=stringop-truncation]
>
> Since the name should always be NUL-terminated, let's use g_strlcpy() to
> silence this warning. And while we're at it, also add an assert() to make
> sure that the provided names always fit the size field (which is fine for
> the current callers, the function is called once with "CORE" and once with
> "LINUX" as a name).
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v3: Do not touch the namesz field
>
> target/s390x/arch_dump.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Thanks, applied.
prev parent reply other threads:[~2021-02-08 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 9:39 [PATCH v3] target/s390x/arch_dump: Fix warning for the name field in the PT_NOTE section Thomas Huth
2021-02-05 10:01 ` Christian Borntraeger
2021-02-08 11:31 ` Cornelia Huck [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=20210208123144.68f6144d.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).