qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] rawhide gcc failures [was: Proposal for deprecating unsupported host OSes & architecutures]
Date: Wed, 22 Mar 2017 14:07:04 -0500	[thread overview]
Message-ID: <c46ff864-fc8b-aeba-30f4-4c773f879786@redhat.com> (raw)
In-Reply-To: <CAFEAcA9pqDoCWrPAJ+KVxLC_eRy-xRg36oYuARYg2YP8VpGpBg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5598 bytes --]

On 03/16/2017 10:23 AM, Peter Maydell wrote:
> OK, here's a concrete proposal for deprecating/dropping out of
> date host OS and architecture support.
> 
> We'll put this in the ChangeLog 'Future incompatible changes'
> section:
> -----
> * Removal of support for untested host OS and architectures:

Tangentially-related: do we officially support bleeding-edge OS builds?
For example, current rawhide has a new-enough gcc that gives some
(possibly-useful) new warnings (-Werror=format-truncation) that fire
when formatting what can be easily proven to be larger than a
fixed-width buffer will hold.  If rawhide is not a current target, then
I don't need to spend any time on this (yet); but if rawhide builds ARE
supported, then we want this patched before 2.9:


  CC      block/blkdebug.o
block/blkdebug.c: In function ‘blkdebug_refresh_filename’:
block/blkdebug.c:693:31: error: ‘%s’ directive output may be truncated
writing up to 4095 bytes into a region of size 4086
[-Werror=format-truncation=]
                  "blkdebug:%s:%s", s->config_file ?: "",
                               ^~
block/blkdebug.c:692:9: note: ‘snprintf’ output 11 or more bytes
(assuming 4106) into a destination of size 4096
         snprintf(bs->exact_filename, sizeof(bs->exact_filename),
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  "blkdebug:%s:%s", s->config_file ?: "",
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  bs->file->bs->exact_filename);
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [/home/dummy/qemu/rules.mak:69: block/blkdebug.o] Error 1
  CC      block/blkverify.o
block/blkverify.c: In function ‘blkverify_refresh_filename’:
block/blkverify.c:309:29: error: ‘%s’ directive output may be truncated
writing up to 4095 bytes into a region of size 4086
[-Werror=format-truncation=]
                  "blkverify:%s:%s",
                             ^~
block/blkverify.c:308:9: note: ‘snprintf’ output between 12 and 8202
bytes into a destination of size 4096
         snprintf(bs->exact_filename, sizeof(bs->exact_filename),
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  "blkverify:%s:%s",
                  ~~~~~~~~~~~~~~~~~~
                  bs->file->bs->exact_filename,
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  s->test_file->bs->exact_filename);
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [/home/dummy/qemu/rules.mak:69: block/blkverify.o] Error 1
  CC      hw/usb/bus.o
hw/usb/bus.c: In function ‘usb_port_location’:
hw/usb/bus.c:410:66: error: ‘%d’ directive output may be truncated
writing between 1 and 11 bytes into a region of size between 0 and 15
[-Werror=format-truncation=]
         snprintf(downstream->path, sizeof(downstream->path), "%s.%d",
                                                                  ^~
hw/usb/bus.c:410:9: note: ‘snprintf’ output between 3 and 28 bytes into
a destination of size 16
         snprintf(downstream->path, sizeof(downstream->path), "%s.%d",
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  upstream->path, portnr);
                  ~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [/home/dummy/qemu/rules.mak:69: hw/usb/bus.o] Error 1
  CC      net/slirp.o
net/slirp.c: In function ‘slirp_smb_cleanup’:
net/slirp.c:565:44: error: ‘%s’ directive output may be truncated
writing up to 127 bytes into a region of size 121
[-Werror=format-truncation=]
         snprintf(cmd, sizeof(cmd), "rm -rf %s", s->smb_dir);
                                            ^~
net/slirp.c:565:9: note: ‘snprintf’ output between 8 and 135 bytes into
a destination of size 128
         snprintf(cmd, sizeof(cmd), "rm -rf %s", s->smb_dir);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
net/slirp.c: In function ‘slirp_smb’:
net/slirp.c:609:46: error: ‘%s’ directive output may be truncated
writing 8 bytes into a region of size between 0 and 127
[-Werror=format-truncation=]
     snprintf(smb_conf, sizeof(smb_conf), "%s/%s", s->smb_dir, "smb.conf");
                                              ^~               ~~~~~~~~~~
net/slirp.c:609:5: note: ‘snprintf’ output between 10 and 137 bytes into
a destination of size 128
     snprintf(smb_conf, sizeof(smb_conf), "%s/%s", s->smb_dir, "smb.conf");
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
net/slirp.c:654:55: error: ‘%s’ directive output may be truncated
writing up to 127 bytes into a region of size 110
[-Werror=format-truncation=]
     snprintf(smb_cmdline, sizeof(smb_cmdline), "%s -l %s -s %s",
                                                       ^~
net/slirp.c:654:5: note: ‘snprintf’ output 23 or more bytes (assuming
150) into a destination of size 128
     snprintf(smb_cmdline, sizeof(smb_cmdline), "%s -l %s -s %s",
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              CONFIG_SMBD_COMMAND, s->smb_dir, smb_conf);
              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [/home/dummy/qemu/rules.mak:69: net/slirp.o] Error 1
make: Target 'all' not remade because of errors.


-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2017-03-22 19:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 15:23 [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Peter Maydell
2017-03-16 15:46 ` Daniel P. Berrange
2017-03-16 15:55   ` Peter Maydell
2017-03-16 16:00     ` Daniel P. Berrange
2017-03-16 16:06       ` Peter Maydell
2017-03-16 16:12         ` Daniel P. Berrange
2017-03-17  9:09       ` Markus Armbruster
2017-03-16 16:52     ` Paolo Bonzini
2017-03-17  9:09       ` Thomas Huth
2017-03-17 10:12         ` Daniel P. Berrange
2017-03-17 10:15           ` Peter Maydell
2017-03-17 10:30             ` Thomas Huth
2017-03-17 10:48               ` Peter Maydell
2017-03-16 18:59     ` Dr. David Alan Gilbert
2017-03-17  9:58       ` Peter Maydell
2017-03-21 17:59   ` Eric Blake
2017-03-16 15:57 ` Gerd Hoffmann
2017-03-16 16:16 ` Daniel P. Berrange
2017-03-16 16:27   ` Peter Maydell
2017-03-16 18:01 ` Peter Maydell
2017-03-16 18:08   ` Daniel P. Berrange
2017-03-22 12:51   ` Alex Bennée
2017-03-22 13:09     ` Peter Maydell
2017-03-22 13:24       ` Thomas Huth
2017-03-23 10:33       ` Paolo Bonzini
2017-03-23 11:02         ` Peter Maydell
2017-03-24  1:28           ` Richard Henderson
2017-03-24 17:24             ` Peter Maydell
2017-03-22 19:07 ` Eric Blake [this message]
2017-03-22 19:39   ` [Qemu-devel] rawhide gcc failures [was: Proposal for deprecating unsupported host OSes & architecutures] Philippe Mathieu-Daudé
2017-03-27  6:36     ` Fam Zheng
2017-03-22 22:33   ` Peter Maydell
2017-03-23  9:25     ` Alex Bennée
2017-03-25 20:49 ` [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Knut Omang
2017-03-25 21:15   ` Peter Maydell
2017-03-26  9:16     ` Knut Omang
2017-03-27 16:32       ` Peter Maydell
2017-03-28 18:34         ` Knut Omang

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=c46ff864-fc8b-aeba-30f4-4c773f879786@redhat.com \
    --to=eblake@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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).