qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Eric Blake" <eblake@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Hacks for building on gcc 7 / Fedora 26
Date: Mon, 17 Jul 2017 16:16:37 +0200	[thread overview]
Message-ID: <1500300997.12570.8.camel@redhat.com> (raw)
In-Reply-To: <39dc6b92-dd56-fe33-cd85-92c03d69f133@redhat.com>

  Hi,

> FWIW, most of these have been fixed in the meantime; the only
> remaining
> hack I had to add was:
> 
> diff --git i/hw/usb/bus.c w/hw/usb/bus.c
> index 5939b273b9..bce011058b 100644
> --- i/hw/usb/bus.c
> +++ w/hw/usb/bus.c
> @@ -407,8 +407,9 @@ void usb_register_companion(const char
> *masterbus,
> USBPort *ports[],
>  void usb_port_location(USBPort *downstream, USBPort *upstream, int
> portnr)
>  {
>      if (upstream) {
> -        snprintf(downstream->path, sizeof(downstream->path),
> "%s.%d",
> -                 upstream->path, portnr);
> +        int l = snprintf(downstream->path, sizeof(downstream->path),
> "%s.%d",
> +                         upstream->path, portnr);
> +        assert(l < sizeof(downstream->path));

Approach looks ok to me.

Maximum hub chain length is 5, number of ports hubs is limited too,
you'll never need more that two digits for port numbers.  So 2*5 plus 4
connecting dots => 14 chars is the max strlen.  path size is 16, so it
will fit, including the terminating \0.

Trying things like "assert(portnr <= 99)" have no effect on the
possible string length calculated by gcc7.

cheers,
  Gerd

  reply	other threads:[~2017-07-17 14:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 14:38 [Qemu-devel] Hacks for building on gcc 7 / Fedora 26 Dr. David Alan Gilbert
2017-04-07 19:21 ` Philippe Mathieu-Daudé
2017-07-13 13:07   ` Philippe Mathieu-Daudé
2017-07-17 13:42     ` Eric Blake
2017-07-17 13:48       ` Eric Blake
2017-07-17 14:16         ` Gerd Hoffmann [this message]
2017-07-17 15:04           ` Eric Blake
2017-07-17 16:46         ` Dr. David Alan Gilbert
2017-07-17 17:22           ` Peter Maydell
2017-07-17 17:29           ` Eric Blake
2017-07-17 17:36             ` Peter Maydell
2017-07-17 18:10               ` Eric Blake
2017-07-17 18:48                 ` Dr. David Alan Gilbert
2017-07-18 15:04               ` Philippe Mathieu-Daudé
2017-07-18 15:10                 ` Eric Blake
2017-07-19  7:15                   ` Thomas Huth
2017-07-17 17:46             ` Dr. David Alan Gilbert
2017-07-18  7:23             ` Daniel P. Berrange
2017-07-18 12:35               ` Eric Blake
2017-07-18 12:56                 ` Daniel P. Berrange
2017-07-18 23:59         ` Richard Henderson
2017-07-19  0:34           ` Eric Blake
2017-04-12 23:54 ` no-reply
2017-07-20 10:50 ` Daniel P. Berrange
2017-07-20 12:10   ` Eric Blake
2017-07-20 16:15   ` Dr. David Alan Gilbert
2017-07-20 16:47     ` Daniel P. Berrange
2017-07-20 17:04       ` Dr. David Alan Gilbert
2017-07-20 17:06         ` Daniel P. Berrange
2017-07-20 18:36           ` Eric Blake

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=1500300997.12570.8.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=f4bug@amsat.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).