qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org, "Ben Pye" <ben@curlybracket.co.uk>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Howard Spoelstra" <hsp.cat7@gmail.com>,
	"Jeff Cody" <jcody@redhat.com>, "Cédric Le Goater" <clg@kaod.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Liu Yuan" <namei.unix@gmail.com>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Max Reitz" <mreitz@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"David Hildenbrand" <david@redhat.com>,
	"David Gibson" <david@gibson.dropbear.id.au>,
	"Markus Armbruster" <armbru@redhat.com>,
	qemu-block@nongnu.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	1803872@bugs.launchpad.net, "Juan Quintela" <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Fix strncpy() warnings for GCC8 new -Wstringop-truncation
Date: Tue, 18 Dec 2018 18:38:09 +0100	[thread overview]
Message-ID: <ea702a96-50bc-22f5-d15c-08e543a4a6fa@redhat.com> (raw)
In-Reply-To: <20181218121457-mutt-send-email-mst@kernel.org>

On 18/12/18 18:17, Michael S. Tsirkin wrote:
> On Tue, Dec 18, 2018 at 06:12:05PM +0100, Paolo Bonzini wrote:
>> On 18/12/18 17:55, Philippe Mathieu-Daudé wrote:
>>>> strpadcpy will instead just silence the warning.
>>> migration/global_state.c:109:15: error: 'strlen' argument 1 declared
>>> attribute 'nonstring' [-Werror=stringop-overflow=]
>>>      s->size = strlen((char *)s->runstate) + 1;
>>>                ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> GCC won... It is true this strlen() is buggy, indeed s->runstate might
>>> be not NUL-terminated.
>>
>> No, runstate is declared as an array of 100 bytes, which are more than
>> enough.  It's ugly code but not buggy.
>>
>> Paolo
> 
> Yes ... but it is loaded using
>         VMSTATE_BUFFER(runstate, GlobalState),
> and parsed using qapi_enum_parse which does not get
> the buffer length.
> 
> So unless we are lucky there's a buffer overrun
> on a remote/file input here.
> 
> Seems buggy to me - what am I missing?

Yup.   I think we're lucky twice though.  First, the state field stops
the runaway qapi_enum_parse.  Second, in any case worst case it's a segv
on migration.  This is a bug but not a CVE.

Paolo

      reply	other threads:[~2018-12-18 17:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 11:03 [Qemu-devel] [PATCH v2 0/3] Fix strncpy() warnings for GCC8 new -Wstringop-truncation Philippe Mathieu-Daudé
2018-12-18 11:03 ` [Qemu-devel] [PATCH v2 1/3] hw/acpi: Replace strncpy() by strpadcpy(pad='\0') Philippe Mathieu-Daudé
2018-12-18 11:09   ` Philippe Mathieu-Daudé
2018-12-18 14:29   ` Igor Mammedov
2018-12-18 11:03 ` [Qemu-devel] [PATCH v2 2/3] block/sheepdog: " Philippe Mathieu-Daudé
2018-12-18 11:03 ` [Qemu-devel] [PATCH v2 3/3] migration: " Philippe Mathieu-Daudé
2018-12-18 14:31 ` [Qemu-devel] [PATCH v2 0/3] Fix strncpy() warnings for GCC8 new -Wstringop-truncation Michael S. Tsirkin
2018-12-18 14:36   ` Daniel P. Berrangé
2018-12-18 14:39   ` Michael S. Tsirkin
2018-12-18 14:45   ` Paolo Bonzini
2018-12-18 14:54     ` Michael S. Tsirkin
2018-12-18 16:38       ` Paolo Bonzini
2018-12-18 17:03         ` Michael S. Tsirkin
2018-12-18 17:38           ` Daniel P. Berrangé
2018-12-18 16:55       ` Philippe Mathieu-Daudé
2018-12-18 17:04         ` Michael S. Tsirkin
2018-12-18 17:12         ` Paolo Bonzini
2018-12-18 17:17           ` Michael S. Tsirkin
2018-12-18 17:38             ` Paolo Bonzini [this message]

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=ea702a96-50bc-22f5-d15c-08e543a4a6fa@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=1803872@bugs.launchpad.net \
    --cc=armbru@redhat.com \
    --cc=ben@curlybracket.co.uk \
    --cc=berrange@redhat.com \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hsp.cat7@gmail.com \
    --cc=imammedo@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=namei.unix@gmail.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=sw@weilnetz.de \
    --cc=thuth@redhat.com \
    /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).