qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Riku Voipio" <riku.voipio@iki.fi>,
	"Laurent Vivier" <laurent@vivier.eu>
Subject: [Qemu-devel] [PULL 3/7] linux-user: avoid string truncation warnings in uname field copying
Date: Fri, 10 May 2019 09:15:53 +0200	[thread overview]
Message-ID: <20190510071557.30126-4-laurent@vivier.eu> (raw)
In-Reply-To: <20190510071557.30126-1-laurent@vivier.eu>

From: Daniel P. Berrangé <berrange@redhat.com>

In file included from /usr/include/string.h:494,
                 from include/qemu/osdep.h:101,
                 from linux-user/uname.c:20:
In function ‘strncpy’,
    inlined from ‘sys_uname’ at linux-user/uname.c:94:3:
/usr/include/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ output may be truncated copying 64 bytes from a string of length 64 [-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

We don't care where the NUL terminator in the original uname
field was. It suffices to copy the entire original field and
simply force a NUL terminator at the end of the new field.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20190501144646.4851-1-berrange@redhat.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
 linux-user/uname.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/linux-user/uname.c b/linux-user/uname.c
index 313b79dbad47..1c05f95387f4 100644
--- a/linux-user/uname.c
+++ b/linux-user/uname.c
@@ -72,9 +72,8 @@ 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); \
-      (dest)[__NEW_UTS_LEN] = '\0'; \
+      memcpy((dest), (src), MIN(sizeof(src), sizeof(dest))); \
+      (dest)[sizeof(dest) - 1] = '\0'; \
   } while (0)
 
 int sys_uname(struct new_utsname *buf)
-- 
2.20.1



  parent reply	other threads:[~2019-05-10  7:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10  7:15 [Qemu-devel] [PULL 0/7] Linux user for 4.1 patches Laurent Vivier
2019-05-10  7:15 ` [Qemu-devel] [PULL 1/7] linux-user: Add missing IPV6 sockopts Laurent Vivier
2019-05-10  7:15 ` [Qemu-devel] [PULL 2/7] linux-user/elfload: Fix GCC 9 build warnings Laurent Vivier
2019-05-10  7:15 ` Laurent Vivier [this message]
2019-05-10  7:15 ` [Qemu-devel] [PULL 4/7] The ioctl(SIOCGIFNAME) call requires a struct ifreq Laurent Vivier
2019-05-10  7:15 ` [Qemu-devel] [PULL 5/7] linux-user: elf: Map empty PT_LOAD segments Laurent Vivier
2019-05-10  7:15 ` [Qemu-devel] [PULL 6/7] linux-user: avoid treading on gprof's SIGPROF signals Laurent Vivier
2019-05-10  7:15 ` [Qemu-devel] [PULL 7/7] linux-user: fix GPROF build failure Laurent Vivier
2019-05-10  9:16 ` [Qemu-devel] [PULL 0/7] Linux user for 4.1 patches Peter Maydell
2019-05-10 10:47   ` 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=20190510071557.30126-4-laurent@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@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 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).