All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1803872@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1803872] Re: gcc 8.2 reports stringop-truncation when building qemu
Date: Wed, 24 Apr 2019 06:01:34 -0000	[thread overview]
Message-ID: <155608569531.13864.14754380970849607768.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 154254872666.7803.12367996737502527787.malonedeb@wampee.canonical.com

** Changed in: qemu
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1803872

Title:
  gcc 8.2 reports stringop-truncation when building qemu

Status in QEMU:
  Fix Released

Bug description:
  QEMU 3.0

  block/sheepdog.c: In function 'find_vdi_name':
  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);
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  If this is the intended behavior, please suppress the warning. For
  example:

  #pragma GCC diagnostic push
  #pragma GCC diagnostic ignored "-Wstringop-truncation"
      strncpy(buf + SD_MAX_VDI_LEN, tag, SD_MAX_VDI_TAG_LEN);
  #pragma GCC diagnostic pop

  This also happens on other sources, for example hw/acpi/core.c, so
  another option is to suppress it globally on CFLAGS (-Wno-stringop-
  truncation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1803872/+subscriptions

  parent reply	other threads:[~2019-04-24  6:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18 13:45 [Qemu-devel] [Bug 1803872] [NEW] gcc 8.2 reports stringop-truncation when building qemu Amir Gonnen
2018-11-18 14:52 ` [Qemu-devel] [Bug 1803872] " Amir Gonnen
2018-12-18 12:42 ` [Qemu-devel] [Bug 1803872] Re: [PATCH v2 3/3] migration: Replace strncpy() by strpadcpy(pad='\0') elmarco
2018-12-18 19:29 ` [Qemu-devel] [Bug 1803872] Re: [PATCH v3 4/5] migration: Use QEMU_NONSTRING for non NUL-terminated arrays Eric Blake
2018-12-18 19:33 ` [Qemu-devel] [Bug 1803872] Re: [PATCH v3 5/5] migration: Use strnlen() for fixed-size string Eric Blake
2018-12-18 21:24   ` [Qemu-devel] " Paolo Bonzini
2018-12-18 21:36 ` [Qemu-devel] [Bug 1803872] Re: [PATCH v3 4/5] migration: Use QEMU_NONSTRING for non NUL-terminated arrays Eric Blake
2019-04-24  6:01 ` Thomas Huth [this message]
2018-12-18 17:51 [Qemu-devel] [PATCH v3 0/5] Fix strncpy() warnings for GCC8 new -Wstringop-truncation Philippe Mathieu-Daudé
2018-12-18 17:51 ` [Qemu-devel] [PATCH v3 1/5] qemu/compiler: Define QEMU_NONSTRING Philippe Mathieu-Daudé
2018-12-18 18:29   ` Eric Blake
2018-12-18 19:28     ` Philippe Mathieu-Daudé
2018-12-18 17:51 ` [Qemu-devel] [PATCH v3 2/5] block/sheepdog: Use QEMU_NONSTRING for non NUL-terminated arrays Philippe Mathieu-Daudé
2018-12-18 18:30   ` Eric Blake
2018-12-18 23:09   ` Michael S. Tsirkin
2018-12-19  9:22     ` Philippe Mathieu-Daudé
2018-12-18 17:51 ` [Qemu-devel] [PATCH v3 3/5] hw/acpi: " Philippe Mathieu-Daudé
2018-12-19  9:15   ` Igor Mammedov
2018-12-19  9:20     ` Philippe Mathieu-Daudé
2018-12-19  9:57       ` Igor Mammedov
2018-12-19 10:10   ` Andrew Jones
2018-12-19 12:43     ` Philippe Mathieu-Daudé
2018-12-19 13:00       ` Andrew Jones
2018-12-20 15:18         ` Igor Mammedov
2018-12-20 16:29           ` Philippe Mathieu-Daudé
2018-12-18 17:51 ` [Qemu-devel] [PATCH v3 4/5] migration: " Philippe Mathieu-Daudé
2019-01-02 11:41   ` Dr. David Alan Gilbert
2018-12-18 17:51 ` [Qemu-devel] [PATCH v3 5/5] migration: Use strnlen() for fixed-size string Philippe Mathieu-Daudé
2018-12-18 23:16   ` Michael S. Tsirkin
2018-12-19  9:24     ` Philippe Mathieu-Daudé
2018-12-18 17:54 ` [Qemu-devel] [PATCH v3 0/5] Fix strncpy() warnings for GCC8 new -Wstringop-truncation Philippe Mathieu-Daudé
2018-12-18 23:08 ` Michael S. Tsirkin
2018-12-24 23:09 ` no-reply

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=155608569531.13864.14754380970849607768.launchpad@wampee.canonical.com \
    --to=1803872@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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.