mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Farman <farman@linux.ibm.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: ruanjinjie <ruanjinjie@huawei.com>,
	"kwankhede@nvidia.com" <kwankhede@nvidia.com>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	"cjia@nvidia.com" <cjia@nvidia.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"akrowiak@linux.ibm.com" <akrowiak@linux.ibm.com>,
	"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
	"jjherne@linux.ibm.com" <jjherne@linux.ibm.com>,
	"mjrosato@linux.ibm.com" <mjrosato@linux.ibm.com>
Subject: Re: [PATCH] vfio/mdev: fix possible memory leak in module init funcs
Date: Fri, 02 Dec 2022 10:08:30 -0500	[thread overview]
Message-ID: <5774398d6f69f0708e1fc040be4b7dd398a884c8.camel@linux.ibm.com> (raw)
In-Reply-To: <BN9PR11MB52763DC62CE7FEB3A70356BD8C179@BN9PR11MB5276.namprd11.prod.outlook.com>

On Fri, 2022-12-02 at 05:28 +0000, Tian, Kevin wrote:
> > From: Alex Williamson <alex.williamson@redhat.com>
> > Sent: Friday, December 2, 2022 5:10 AM
> > 
> > > Otherwise what this patch does looks better IMHO:
> > > 
> > >         ret = device_register(&dev);
> > >         if (ret) {
> > >                 put_device(&dev);
> > >                 goto err1;
> > >         }
> > > 
> > >         ...
> > > 
> > >         return 0;
> > > 
> > > err2:
> > >         device_unregister(&dev);
> > > err1:
> > >         earlier_unwind();
> > > 
> > 
> > This is essentially what was originally proposed.  It could also be
> > called a "mixed model", implementing part of the unwind in the
> > error
> > branch before jumping to the common unwind.  As demonstrated below,
> > every current vfio driver calling device_register() follows a
> > similar
> > goto unwind stack as found in the sample drivers, which makes it
> > trivially easy to split the device_unregister() call and add a goto
> > target in between.
> 
> OK. Actually looking into other users of device_register() I can
> see both schemes are used, so...
> 
> > 
> > Either way, they're equivalent and I'll take whichever version
> > addresses all the vfio related use cases and gets acks from their
> > maintainers.  Thanks,
> 
> ... agree either way is fine. Since your version fixes all vfio
> cases,
> feel free to include:
> 
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
> 
> > 
> > Alex
> > 
> > diff --git a/drivers/s390/cio/vfio_ccw_drv.c
> > b/drivers/s390/cio/vfio_ccw_drv.c
> > index c2a65808605a..54aba7cceb33 100644
> > --- a/drivers/s390/cio/vfio_ccw_drv.c
> > +++ b/drivers/s390/cio/vfio_ccw_drv.c
> > @@ -199,8 +199,9 @@ static int vfio_ccw_sch_probe(struct subchannel
> > *sch)
> >         return 0;
> > 
> >  out_unreg:
> > -       device_unregister(&parent->dev);
> > +       device_del(&parent->dev);
> >  out_free:
> > +       put_device(&parent->dev);
> >         dev_set_drvdata(&sch->dev, NULL);
> >         return ret;
> >  }

Ugh, sorry. I had this partially right at one point but missed this
scenario when fixing the parts I had wrong.

This is fine by me, thanks for the fixup:

Reviewed-by: Eric Farman <farman@linux.ibm.com>

> > diff --git a/drivers/s390/crypto/vfio_ap_drv.c
> > b/drivers/s390/crypto/vfio_ap_drv.c
> > index f43cfeabd2cc..997b524bdd2b 100644
> > --- a/drivers/s390/crypto/vfio_ap_drv.c
> > +++ b/drivers/s390/crypto/vfio_ap_drv.c
> > @@ -122,7 +122,7 @@ static int vfio_ap_matrix_dev_create(void)
> >         return 0;
> > 
> >  matrix_drv_err:
> > -       device_unregister(&matrix_dev->device);
> > +       device_del(&matrix_dev->device);
> >  matrix_reg_err:
> >         put_device(&matrix_dev->device);
> >  matrix_alloc_err:
> > diff --git a/samples/vfio-mdev/mbochs.c b/samples/vfio-
> > mdev/mbochs.c
> > index 8b5a3a778a25..e54eb752e1ba 100644
> > --- a/samples/vfio-mdev/mbochs.c
> > +++ b/samples/vfio-mdev/mbochs.c
> > @@ -1430,7 +1430,7 @@ static int __init mbochs_dev_init(void)
> > 
> >         ret = device_register(&mbochs_dev);
> >         if (ret)
> > -               goto err_class;
> > +               goto err_put;
> > 
> >         ret = mdev_register_parent(&mbochs_parent, &mbochs_dev,
> > &mbochs_driver,
> >                                    mbochs_mdev_types,
> > @@ -1441,8 +1441,9 @@ static int __init mbochs_dev_init(void)
> >         return 0;
> > 
> >  err_device:
> > -       device_unregister(&mbochs_dev);
> > -err_class:
> > +       device_del(&mbochs_dev);
> > +err_put:
> > +       put_device(&mbochs_dev);
> >         class_destroy(mbochs_class);
> >  err_driver:
> >         mdev_unregister_driver(&mbochs_driver);
> > diff --git a/samples/vfio-mdev/mdpy.c b/samples/vfio-mdev/mdpy.c
> > index 721fb06c6413..e8400fdab71d 100644
> > --- a/samples/vfio-mdev/mdpy.c
> > +++ b/samples/vfio-mdev/mdpy.c
> > @@ -717,7 +717,7 @@ static int __init mdpy_dev_init(void)
> > 
> >         ret = device_register(&mdpy_dev);
> >         if (ret)
> > -               goto err_class;
> > +               goto err_put;
> > 
> >         ret = mdev_register_parent(&mdpy_parent, &mdpy_dev,
> > &mdpy_driver,
> >                                    mdpy_mdev_types,
> > @@ -728,8 +728,9 @@ static int __init mdpy_dev_init(void)
> >         return 0;
> > 
> >  err_device:
> > -       device_unregister(&mdpy_dev);
> > -err_class:
> > +       device_del(&mdpy_dev);
> > +err_put:
> > +       put_device(&mdpy_dev);
> >         class_destroy(mdpy_class);
> >  err_driver:
> >         mdev_unregister_driver(&mdpy_driver);
> > diff --git a/samples/vfio-mdev/mtty.c b/samples/vfio-mdev/mtty.c
> > index 3c2a421b9b69..e887de672c52 100644
> > --- a/samples/vfio-mdev/mtty.c
> > +++ b/samples/vfio-mdev/mtty.c
> > @@ -1330,7 +1330,7 @@ static int __init mtty_dev_init(void)
> > 
> >         ret = device_register(&mtty_dev.dev);
> >         if (ret)
> > -               goto err_class;
> > +               goto err_put;
> > 
> >         ret = mdev_register_parent(&mtty_dev.parent, &mtty_dev.dev,
> >                                    &mtty_driver, mtty_mdev_types,
> > @@ -1340,8 +1340,9 @@ static int __init mtty_dev_init(void)
> >         return 0;
> > 
> >  err_device:
> > -       device_unregister(&mtty_dev.dev);
> > -err_class:
> > +       device_del(&mtty_dev.dev);
> > +err_put:
> > +       put_device(&mtty_dev.dev);
> >         class_destroy(mtty_dev.vd_class);
> >  err_driver:
> >         mdev_unregister_driver(&mtty_driver);
> 


  reply	other threads:[~2022-12-02 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  3:28 ruanjinjie
2022-11-30  1:17 ` Ruan Jinjie
2022-11-30 23:06 ` Alex Williamson
2022-12-01  2:00   ` Tian, Kevin
2022-12-01 21:10     ` Alex Williamson
2022-12-02  5:28       ` Tian, Kevin
2022-12-02 15:08         ` Eric Farman [this message]
2022-12-01  2:11   ` Ruan Jinjie

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=5774398d6f69f0708e1fc040be4b7dd398a884c8.camel@linux.ibm.com \
    --to=farman@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=jjherne@linux.ibm.com \
    --cc=kevin.tian@intel.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=ruanjinjie@huawei.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

all inboxes | Powered by JetHome®