From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Juan Quintela <quintela@redhat.com>,
Jeff Cody <jcody@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Liu Yuan <namei.unix@gmail.com>
Subject: Re: [Qemu-devel] [PATCH for-3.1? 1/3] sheepdog: fix stringop-truncation warning
Date: Tue, 20 Nov 2018 20:35:55 +0100 [thread overview]
Message-ID: <3e048f60-a589-9ddc-2bbf-2cbbdcf01939@redhat.com> (raw)
In-Reply-To: <20181120152753.10463-2-marcandre.lureau@redhat.com>
On 20/11/18 16:27, Marc-André Lureau wrote:
> It seems adding an assert is enough to silence GCC.
> (sd_parse_snapid_or_tag() g_strlcpy() ensures that we don't get in
> that situation)
>
> ~/src/qemu/block/sheepdog.c: In function 'find_vdi_name':
> ~/src/qemu/block/sheepdog.c:1239:5: error: 'strncpy' specified bound 256 equals destination size [-Werror=stringop-truncation]
> strncpy(buf + SD_MAX_VDI_LEN, tag, SD_MAX_VDI_TAG_LEN);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
Fixes: https://bugs.launchpad.net/bugs/1803872
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> block/sheepdog.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/block/sheepdog.c b/block/sheepdog.c
> index 0125df9d49..f8877b611d 100644
> --- a/block/sheepdog.c
> +++ b/block/sheepdog.c
> @@ -1236,6 +1236,7 @@ static int find_vdi_name(BDRVSheepdogState *s, const char *filename,
> * don't want the send_req to read uninitialized data.
> */
> strncpy(buf, filename, SD_MAX_VDI_LEN);
> + assert(strlen(tag) < SD_MAX_VDI_TAG_LEN);
> strncpy(buf + SD_MAX_VDI_LEN, tag, SD_MAX_VDI_TAG_LEN);
>
> memset(&hdr, 0, sizeof(hdr));
>
I tried to fix this warning this way:
- char buf[SD_MAX_VDI_LEN + SD_MAX_VDI_TAG_LEN];
+ struct {
+ char vdi[SD_MAX_VDI_LEN];
+ char vdi_tag[SD_MAX_VDI_TAG_LEN];
+ } buf;
...
- strncpy(buf, filename, SD_MAX_VDI_LEN);
- strncpy(buf + SD_MAX_VDI_LEN, tag, SD_MAX_VDI_TAG_LEN);
+ strncpy(buf.vdi, filename, SD_MAX_VDI_LEN);
+ strncpy(buf.vdi_tag, tag, SD_MAX_VDI_TAG_LEN);
but your patch is simpler.
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Thanks,
Phil.
next prev parent reply other threads:[~2018-11-20 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 15:27 [Qemu-devel] [PATCH for-3.1? 0/3] strcpy: fix stringop-truncation warnings Marc-André Lureau
2018-11-20 15:27 ` [Qemu-devel] [PATCH for-3.1? 1/3] sheepdog: fix stringop-truncation warning Marc-André Lureau
2018-11-20 16:56 ` Eric Blake
2018-11-20 19:35 ` Philippe Mathieu-Daudé [this message]
2018-11-20 15:27 ` [Qemu-devel] [PATCH for-3.1? 2/3] migration: " Marc-André Lureau
2018-11-20 17:01 ` Eric Blake
2018-11-20 17:22 ` Dr. David Alan Gilbert
2018-11-20 17:24 ` Marc-André Lureau
2018-11-20 17:25 ` Dr. David Alan Gilbert
2018-11-20 19:37 ` Philippe Mathieu-Daudé
2018-11-20 15:27 ` [Qemu-devel] [PATCH for-3.1? 3/3] acpi: fix stringop-truncation warnings Marc-André Lureau
2018-11-20 17:03 ` Eric Blake
2018-11-20 19:45 ` Philippe Mathieu-Daudé
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=3e048f60-a589-9ddc-2bbf-2cbbdcf01939@redhat.com \
--to=philmd@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).