qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 1/1] block/nvme: fix Coverity reports
Date: Mon, 21 May 2018 14:21:10 +0800	[thread overview]
Message-ID: <20180521062109.GG17725@lemon.usersys.redhat.com> (raw)
In-Reply-To: <CAFEAcA8xWPjuQipfEyv-6KHTjhQ=LuyDi5Zx3r4X28JHZAVw0w@mail.gmail.com>

On Fri, 05/18 19:01, Peter Maydell wrote:
> On 1 March 2018 at 07:54, Fam Zheng <famz@redhat.com> wrote:
> > From: Paolo Bonzini <pbonzini@redhat.com>
> >
> > 1) string not null terminated in sysfs_find_group_file
> >
> > 2) NULL pointer dereference and dead local variable in nvme_init.
> >
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> >
> > Message-Id: <20180213015240.9352-1-famz@redhat.com>
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> 
> Hi. It looks like Coverity still doesn't like the error-exit
> handling in nvme_init() (CID 1385847):
> 
> > ---
> >  block/nvme.c        | 10 +++++++---
> >  util/vfio-helpers.c |  2 +-
> >  2 files changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/block/nvme.c b/block/nvme.c
> > index 10bffbbf2f..75078022f6 100644
> > --- a/block/nvme.c
> > +++ b/block/nvme.c
> > @@ -645,7 +645,7 @@ static int nvme_init(BlockDriverState *bs, const char *device, int namespace,
> >      aio_set_event_notifier(bdrv_get_aio_context(bs), &s->irq_notifier,
> >                             false, nvme_handle_event, nvme_poll_cb);
> >
> > -    nvme_identify(bs, namespace, errp);
> > +    nvme_identify(bs, namespace, &local_err);
> >      if (local_err) {
> >          error_propagate(errp, local_err);
> >          ret = -EIO;
> > @@ -666,8 +666,12 @@ fail_queue:
> >      nvme_free_queue_pair(bs, s->queues[0]);
> >  fail:
> >      g_free(s->queues);
> > -    qemu_vfio_pci_unmap_bar(s->vfio, 0, (void *)s->regs, 0, NVME_BAR_SIZE);
> > -    qemu_vfio_close(s->vfio);
> > +    if (s->regs) {
> > +        qemu_vfio_pci_unmap_bar(s->vfio, 0, (void *)s->regs, 0, NVME_BAR_SIZE);
> 
> We can get here with s->vfio being NULL and s->regs being
> uninitialized, but qemu_vfio_pci_unmap_bar() will unconditionally
> dereference s->vfio.
> 
> If you want to write the error path like this I think you need
> to initialize s->regs = NULL before we do the qemu_vfio_open_pci()
> call and error-check.

Block layer uses g_malloc0 to allocate *s, so we expect s->regs is NULL to begin
with. But I can send a patch to explicitly initialize it to NULL to make the
code simpler to reason.

Fam

> 
> > +    }
> > +    if (s->vfio) {
> > +        qemu_vfio_close(s->vfio);
> > +    }
> >      event_notifier_cleanup(&s->irq_notifier);
> >      return ret;
> >  }
> 
> thanks
> -- PMM

  reply	other threads:[~2018-05-21  6:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01  7:54 [Qemu-devel] [PULL 0/1] Block patches 2018-03-01 Fam Zheng
2018-03-01  7:54 ` [Qemu-devel] [PULL 1/1] block/nvme: fix Coverity reports Fam Zheng
2018-05-18 18:01   ` Peter Maydell
2018-05-21  6:21     ` Fam Zheng [this message]
2018-03-01 14:43 ` [Qemu-devel] [PULL 0/1] Block patches 2018-03-01 Peter Maydell

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=20180521062109.GG17725@lemon.usersys.redhat.com \
    --to=famz@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).