All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"alistair23@gmail.com" <alistair23@gmail.com>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	"riku.voipio@iki.fi" <riku.voipio@iki.fi>,
	"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-trivial] [PATCH v2 4/5] linux-user/uname: Fix GCC 9 build warnings
Date: Wed, 1 May 2019 10:44:53 +0100	[thread overview]
Message-ID: <20190501094452.GQ29808@redhat.com> (raw)
In-Reply-To: <503a1f5f-7dad-1e4e-e1b1-aaeeeac9739f@vivier.eu>

On Wed, May 01, 2019 at 11:40:13AM +0200, Laurent Vivier wrote:
> On 01/05/2019 01:28, Alistair Francis wrote:
> > Fix this warning when building with GCC9 on Fedora 30:
> > In function ‘strncpy’,
> >     inlined from ‘sys_uname’ at /home/alistair/qemu/linux-user/uname.c:94:3:
> > /usr/include/bits/string_fortified.h:106:10: error: ‘__builtin_strncpy’ output may be truncated copying 64 bytes from a string of length 64 [-Werror=stringop-truncation]
> >   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
> >       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > 
> > Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> > ---
> >  linux-user/uname.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/linux-user/uname.c b/linux-user/uname.c
> > index 313b79dbad..2fc6096a5b 100644
> > --- a/linux-user/uname.c
> > +++ b/linux-user/uname.c
> > @@ -73,7 +73,7 @@ const char *cpu_to_uname_machine(void *cpu_env)
> >  #define COPY_UTSNAME_FIELD(dest, src) \
> >    do { \
> >        /* __NEW_UTS_LEN doesn't include terminating null */ \
> > -      (void) strncpy((dest), (src), __NEW_UTS_LEN); \
> > +      (void) memcpy((dest), (src), MIN(strlen(src), __NEW_UTS_LEN)); \
> 
> You should use MIN(strlen(src) + 1, __NEW_UTS_LEN) to copy the NUL
> character if it is present and fit in __NEW_UTS_LEN.

IMHO we shouldn't use strlen at all. I proposed fixing it using sizeof()
instead here:

  https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg02154.html

> 
> >        (dest)[__NEW_UTS_LEN] = '\0'; \
> >    } while (0)

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"alistair23@gmail.com" <alistair23@gmail.com>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	"riku.voipio@iki.fi" <riku.voipio@iki.fi>,
	"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 4/5] linux-user/uname: Fix GCC 9 build warnings
Date: Wed, 1 May 2019 10:44:53 +0100	[thread overview]
Message-ID: <20190501094452.GQ29808@redhat.com> (raw)
In-Reply-To: <503a1f5f-7dad-1e4e-e1b1-aaeeeac9739f@vivier.eu>

On Wed, May 01, 2019 at 11:40:13AM +0200, Laurent Vivier wrote:
> On 01/05/2019 01:28, Alistair Francis wrote:
> > Fix this warning when building with GCC9 on Fedora 30:
> > In function ‘strncpy’,
> >     inlined from ‘sys_uname’ at /home/alistair/qemu/linux-user/uname.c:94:3:
> > /usr/include/bits/string_fortified.h:106:10: error: ‘__builtin_strncpy’ output may be truncated copying 64 bytes from a string of length 64 [-Werror=stringop-truncation]
> >   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
> >       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > 
> > Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> > ---
> >  linux-user/uname.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/linux-user/uname.c b/linux-user/uname.c
> > index 313b79dbad..2fc6096a5b 100644
> > --- a/linux-user/uname.c
> > +++ b/linux-user/uname.c
> > @@ -73,7 +73,7 @@ const char *cpu_to_uname_machine(void *cpu_env)
> >  #define COPY_UTSNAME_FIELD(dest, src) \
> >    do { \
> >        /* __NEW_UTS_LEN doesn't include terminating null */ \
> > -      (void) strncpy((dest), (src), __NEW_UTS_LEN); \
> > +      (void) memcpy((dest), (src), MIN(strlen(src), __NEW_UTS_LEN)); \
> 
> You should use MIN(strlen(src) + 1, __NEW_UTS_LEN) to copy the NUL
> character if it is present and fit in __NEW_UTS_LEN.

IMHO we shouldn't use strlen at all. I proposed fixing it using sizeof()
instead here:

  https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg02154.html

> 
> >        (dest)[__NEW_UTS_LEN] = '\0'; \
> >    } while (0)

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	"riku.voipio@iki.fi" <riku.voipio@iki.fi>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	"alistair23@gmail.com" <alistair23@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2 4/5] linux-user/uname: Fix GCC 9 build warnings
Date: Wed, 1 May 2019 10:44:53 +0100	[thread overview]
Message-ID: <20190501094452.GQ29808@redhat.com> (raw)
Message-ID: <20190501094453.Ci0in6NQtgMfEqRCqviLHudXVP1hxtReRR8UTmqQ8JM@z> (raw)
In-Reply-To: <503a1f5f-7dad-1e4e-e1b1-aaeeeac9739f@vivier.eu>

On Wed, May 01, 2019 at 11:40:13AM +0200, Laurent Vivier wrote:
> On 01/05/2019 01:28, Alistair Francis wrote:
> > Fix this warning when building with GCC9 on Fedora 30:
> > In function ‘strncpy’,
> >     inlined from ‘sys_uname’ at /home/alistair/qemu/linux-user/uname.c:94:3:
> > /usr/include/bits/string_fortified.h:106:10: error: ‘__builtin_strncpy’ output may be truncated copying 64 bytes from a string of length 64 [-Werror=stringop-truncation]
> >   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
> >       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > 
> > Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> > ---
> >  linux-user/uname.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/linux-user/uname.c b/linux-user/uname.c
> > index 313b79dbad..2fc6096a5b 100644
> > --- a/linux-user/uname.c
> > +++ b/linux-user/uname.c
> > @@ -73,7 +73,7 @@ const char *cpu_to_uname_machine(void *cpu_env)
> >  #define COPY_UTSNAME_FIELD(dest, src) \
> >    do { \
> >        /* __NEW_UTS_LEN doesn't include terminating null */ \
> > -      (void) strncpy((dest), (src), __NEW_UTS_LEN); \
> > +      (void) memcpy((dest), (src), MIN(strlen(src), __NEW_UTS_LEN)); \
> 
> You should use MIN(strlen(src) + 1, __NEW_UTS_LEN) to copy the NUL
> character if it is present and fit in __NEW_UTS_LEN.

IMHO we shouldn't use strlen at all. I proposed fixing it using sizeof()
instead here:

  https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg02154.html

> 
> >        (dest)[__NEW_UTS_LEN] = '\0'; \
> >    } while (0)

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


  reply	other threads:[~2019-05-01  9:45 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 23:28 [Qemu-trivial] [PATCH v2 0/5] Fix some GCC 9 build warnings Alistair Francis
2019-04-30 23:28 ` [Qemu-devel] " Alistair Francis
2019-04-30 23:28 ` Alistair Francis
2019-04-30 23:28 ` [Qemu-trivial] [PATCH v2 1/5] util/qemu-sockets: Fix " Alistair Francis
2019-04-30 23:28   ` [Qemu-devel] " Alistair Francis
2019-04-30 23:28   ` Alistair Francis
2019-05-01  9:35   ` [Qemu-trivial] " Laurent Vivier
2019-05-01  9:35     ` [Qemu-devel] " Laurent Vivier
2019-05-01  9:35     ` Laurent Vivier
2019-05-01  9:41   ` [Qemu-trivial] " Daniel P. Berrangé
2019-05-01  9:41     ` [Qemu-devel] " Daniel P. Berrangé
2019-05-01  9:41     ` Daniel P. Berrangé
2019-05-02 17:57     ` [Qemu-trivial] " Alistair Francis
2019-05-02 17:57       ` [Qemu-devel] " Alistair Francis
2019-05-02 17:57       ` Alistair Francis
2019-04-30 23:28 ` [Qemu-trivial] [PATCH v2 2/5] hw/usb/hcd-xhci: Fix GCC 9 build warning Alistair Francis
2019-04-30 23:28   ` [Qemu-devel] " Alistair Francis
2019-04-30 23:28   ` Alistair Francis
2019-05-01  9:37   ` [Qemu-trivial] " Laurent Vivier
2019-05-01  9:37     ` [Qemu-devel] " Laurent Vivier
2019-05-01  9:37     ` Laurent Vivier
2019-05-01  9:43   ` [Qemu-trivial] " Daniel P. Berrangé
2019-05-01  9:43     ` [Qemu-devel] " Daniel P. Berrangé
2019-05-01  9:43     ` Daniel P. Berrangé
2019-05-01 14:12   ` [Qemu-trivial] " Richard Henderson
2019-05-01 14:12     ` Richard Henderson
2019-05-01 14:12     ` Richard Henderson
2019-05-01 15:21     ` [Qemu-trivial] " Philippe Mathieu-Daudé
2019-05-01 15:21       ` Philippe Mathieu-Daudé
2019-05-02 17:53     ` [Qemu-trivial] " Alistair Francis
2019-05-02 17:53       ` Alistair Francis
2019-05-02 17:53       ` Alistair Francis
2019-04-30 23:28 ` [Qemu-trivial] [PATCH v2 3/5] hw/usb/dev-mtp: " Alistair Francis
2019-04-30 23:28   ` [Qemu-devel] " Alistair Francis
2019-04-30 23:28   ` Alistair Francis
2019-05-01  7:12   ` [Qemu-trivial] " Thomas Huth
2019-05-01  7:12     ` Thomas Huth
2019-05-01  7:12     ` Thomas Huth
2019-05-01  9:40   ` [Qemu-trivial] " Daniel P. Berrangé
2019-05-01  9:40     ` [Qemu-devel] " Daniel P. Berrangé
2019-05-01  9:40     ` Daniel P. Berrangé
2019-05-02 17:48     ` [Qemu-trivial] " Alistair Francis
2019-05-02 17:48       ` [Qemu-devel] " Alistair Francis
2019-05-02 17:48       ` Alistair Francis
2019-04-30 23:28 ` [Qemu-trivial] [PATCH v2 4/5] linux-user/uname: Fix GCC 9 build warnings Alistair Francis
2019-04-30 23:28   ` [Qemu-devel] " Alistair Francis
2019-04-30 23:28   ` Alistair Francis
2019-05-01  9:40   ` [Qemu-trivial] " Laurent Vivier
2019-05-01  9:40     ` [Qemu-devel] " Laurent Vivier
2019-05-01  9:40     ` Laurent Vivier
2019-05-01  9:44     ` Daniel P. Berrangé [this message]
2019-05-01  9:44       ` Daniel P. Berrangé
2019-05-01  9:44       ` Daniel P. Berrangé
2019-05-01  9:46       ` [Qemu-trivial] " Laurent Vivier
2019-05-01  9:46         ` [Qemu-devel] " Laurent Vivier
2019-05-01  9:46         ` Laurent Vivier
2019-05-01 12:00     ` [Qemu-trivial] " Eric Blake
2019-05-01 12:00       ` Eric Blake
2019-05-02 17:24       ` [Qemu-trivial] " Alistair Francis
2019-05-02 17:24         ` Alistair Francis
2019-05-02 17:24         ` Alistair Francis
2019-04-30 23:29 ` [Qemu-trivial] [PATCH v2 5/5] linux-user/elfload: " Alistair Francis
2019-04-30 23:29   ` [Qemu-devel] " Alistair Francis
2019-04-30 23:29   ` Alistair Francis
2019-05-01  9:40   ` [Qemu-trivial] " Laurent Vivier
2019-05-01  9:40     ` [Qemu-devel] " Laurent Vivier
2019-05-01  9:40     ` Laurent Vivier
2019-05-01 14:15   ` [Qemu-trivial] " Richard Henderson
2019-05-01 14:15     ` Richard Henderson
2019-05-01 14:15     ` Richard Henderson
2019-05-02  8:14   ` [Qemu-trivial] " Laurent Vivier
2019-05-02  8:14     ` [Qemu-devel] " Laurent Vivier
2019-05-02  8:14     ` Laurent Vivier

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=20190501094452.GQ29808@redhat.com \
    --to=berrange@redhat.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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.