qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Farhan Ali <alifm@linux.ibm.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
	Eric Farman <farman@linux.ibm.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5] vfio-ccw: support async command subregion
Date: Wed, 12 Jun 2019 11:38:08 +0200	[thread overview]
Message-ID: <20190612113808.06fec7d7.cohuck@redhat.com> (raw)
In-Reply-To: <e07bf42d-2b8a-382c-85c8-520985ddfe8a@linux.ibm.com>

On Tue, 11 Jun 2019 15:33:59 -0400
Farhan Ali <alifm@linux.ibm.com> wrote:

> On 06/07/2019 10:53 AM, Cornelia Huck wrote:
> > A vfio-ccw device may provide an async command subregion for
> > issuing halt/clear subchannel requests. If it is present, use
> > it for sending halt/clear request to the device; if not, fall
> > back to emulation (as done today).
> > 
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> > 
> > v4->v5:
> > - It seems we need to take the indirection via the class for the
> >    callbacks after all :(
> > - Dropped Eric's R-b: for that reason
> > 
> > ---
> >   hw/s390x/css.c              |  27 +++++++--
> >   hw/s390x/s390-ccw.c         |  20 +++++++
> >   hw/vfio/ccw.c               | 112 +++++++++++++++++++++++++++++++++++-
> >   include/hw/s390x/css.h      |   3 +
> >   include/hw/s390x/s390-ccw.h |   2 +
> >   5 files changed, 158 insertions(+), 6 deletions(-)
> > 

> > @@ -309,11 +400,26 @@ static void vfio_ccw_get_region(VFIOCCWDevice *vcdev, Error **errp)
> >       vcdev->io_region_offset = info->offset;
> >       vcdev->io_region = g_malloc0(info->size);
> >   
> > +    /* check for the optional async command region */
> > +    ret = vfio_get_dev_region_info(vdev, VFIO_REGION_TYPE_CCW,
> > +                                   VFIO_REGION_SUBTYPE_CCW_ASYNC_CMD, &info);
> > +    if (!ret) {
> > +        vcdev->async_cmd_region_size = info->size;
> > +        if (sizeof(*vcdev->async_cmd_region) != vcdev->async_cmd_region_size) {
> > +            error_setg(errp, "vfio: Unexpected size of the async cmd region");
> > +            g_free(info);
> > +            return;
> > +        }
> > +        vcdev->async_cmd_region_offset = info->offset;
> > +        vcdev->async_cmd_region = g_malloc0(info->size);
> > +    }
> > +
> >       g_free(info);
> >   }
> >   
> >   static void vfio_ccw_put_region(VFIOCCWDevice *vcdev)
> >   {
> > +    g_free(vcdev->async_cmd_region);
> >       g_free(vcdev->io_region);
> >   }  
> 
> I think we can have a memory leak given how the code is currently 
> structured and how we call vfio_ccw_get_region.
> 
> vfio_ccw_get_region is called in vfio_ccw_realize. So if we return an 
> error from vfio_ccw_get_region, we would jump to out_region_err in 
> vfio_ccw_realize which would call vfio_ccw_put_device.
> 
> Now we can also return an error from vfio_ccw_get_region for the async 
> region, and so we might never end up freeing the io_region for which we 
> allocated memory successfully.
> 
> I think we would also need to change vfio_ccw_realize, no?

Indeed, you're right. I have the following change on top:

diff --git a/hw/vfio/ccw.c b/hw/vfio/ccw.c
index c9d1c76b4d04..d21ac24f743c 100644
--- a/hw/vfio/ccw.c
+++ b/hw/vfio/ccw.c
@@ -407,6 +407,7 @@ static void vfio_ccw_get_region(VFIOCCWDevice *vcdev, Error **errp)
         vcdev->async_cmd_region_size = info->size;
         if (sizeof(*vcdev->async_cmd_region) != vcdev->async_cmd_region_size) {
             error_setg(errp, "vfio: Unexpected size of the async cmd region");
+            g_free(vcdev->io_region);
             g_free(info);
             return;
         }

Anything else before I respin?


  reply	other threads:[~2019-06-12  9:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 14:53 [Qemu-devel] [PATCH v5] vfio-ccw: support async command subregion Cornelia Huck
2019-06-07 15:02 ` Farhan Ali
2019-06-07 15:09   ` Cornelia Huck
2019-06-07 15:19     ` Farhan Ali
2019-06-11 11:37       ` Cornelia Huck
2019-06-11 19:37         ` Farhan Ali
2019-06-11 19:33 ` Farhan Ali
2019-06-12  9:38   ` Cornelia Huck [this message]
2019-06-12 16:14     ` Farhan Ali

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=20190612113808.06fec7d7.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=farman@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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).