qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	qemu-stable@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Cam Macdonell <cam@cs.ualberta.ca>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] ivshmem: add missing error exit(2)
Date: Wed, 12 Jun 2013 10:49:17 +0200	[thread overview]
Message-ID: <51B8360D.8060603@suse.de> (raw)
In-Reply-To: <20130603131132.GA29131@stefanha-thinkpad.redhat.com>

Am 03.06.2013 15:11, schrieb Stefan Hajnoczi:
> On Mon, Jun 03, 2013 at 06:26:22AM -0600, Eric Blake wrote:
>> On 06/03/2013 02:58 AM, Stefan Hajnoczi wrote:
>>> If the user fails to specify 'chardev' or 'shm' then we cannot continue.
>>> Exit right away so that we don't invoke shm_open(3) with a NULL pointer.
>>>
>>> It would be nice to replace exit(1) with error returns in the PCI device
>>> .init() function, but leave that for another patch since exit(1) is
>>> currently used elsewhere.
>>>
>>> Spotted by Coverity.
>>>
>>> Cc: Cam Macdonell <cam@cs.ualberta.ca>
>>> Cc: qemu-stable@nongnu.org
>>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>>> ---
>>>  hw/misc/ivshmem.c | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/hw/misc/ivshmem.c b/hw/misc/ivshmem.c
>>> index a19a6d6..5658f73 100644
>>> --- a/hw/misc/ivshmem.c
>>> +++ b/hw/misc/ivshmem.c
>>> @@ -735,6 +735,7 @@ static int pci_ivshmem_init(PCIDevice *dev)
>>>  
>>>          if (s->shmobj == NULL) {
>>>              fprintf(stderr, "Must specify 'chardev' or 'shm' to ivshmem\n");
>>> +            exit(1);
>>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>>
>> However, I prefer exit(EXIT_FAILURE) rather than exit(1), to make it a
>> bit easier to grep for known failure exits.  Libvirt has a syntax
>> checker (taken from gnulib) that enforces such a style, if qemu would
>> like to adopt that style.
> 
> I like EXIT_FAILURE too but the rest of the file inconsistently uses
> exit(1) and exit(-1).  I decided exit(1) was the least evil but the
> longer term fix is to return instead of exiting.

QOM realize would solve that, but similar to virtio the PCI qdev initfn
actually does something (allocating the config region among others) so
faces the same design questions of how to best inherit QOM methods as
currently being discussed. Shouldn't hold up a bug fix like this one.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-06-12  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  8:58 [Qemu-devel] [PATCH v2 0/2] vhost-scsi and ivshmem fixes for Coverity issues Stefan Hajnoczi
2013-06-03  8:58 ` [Qemu-devel] [PATCH v2 1/2] vhost-scsi: fix k->set_guest_notifiers() NULL dereference Stefan Hajnoczi
2013-06-03  9:07   ` Paolo Bonzini
2013-06-03  8:58 ` [Qemu-devel] [PATCH v2 2/2] ivshmem: add missing error exit(2) Stefan Hajnoczi
2013-06-03 12:26   ` Eric Blake
2013-06-03 13:11     ` Stefan Hajnoczi
2013-06-12  8:49       ` Andreas Färber [this message]
2013-06-12  7:22   ` Stefan Hajnoczi
2013-06-12  9:18     ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev

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=51B8360D.8060603@suse.de \
    --to=afaerber@suse.de \
    --cc=cam@cs.ualberta.ca \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@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).