Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: Alexey Khoroshilov <khoroshilov@ispras.ru>,
	Neo Jia <cjia@nvidia.com>, <kvm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <ldv-project@linuxtesting.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] samples/vfio-mdev: don't return zero on failure paths in mtty_dev_init()
Date: Wed, 4 Jan 2017 08:30:41 -0700	[thread overview]
Message-ID: <20170104083041.312f4b94@t450s.home> (raw)
In-Reply-To: <a20e1de8-7d88-d5d1-e837-1de75a306e41@nvidia.com>

On Wed, 4 Jan 2017 17:52:30 +0530
Kirti Wankhede <kwankhede@nvidia.com> wrote:

> Dan Carpenter had sent similar change earlier.
> https://www.spinics.net/lists/kvm/msg141470.html
> 
> Alex,
> Did you pull that change in your tree?

I had somehow missed Dan's patch.  I'll apply Dan's with a Reported-by
credit for Alexey as well.  Thanks,

Alex

> On 12/31/2016 4:10 AM, Alexey Khoroshilov wrote:
> > If class_create() or mdev_register_device() fail, mtty_dev_init()
> > breaks off initialization, deallocates all resources, but returns zero.
> > 
> > The patch adds proper error code return values.
> > 
> > Found by Linux Driver Verification project (linuxtesting.org).
> > 
> > Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> > ---
> >  samples/vfio-mdev/mtty.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/samples/vfio-mdev/mtty.c b/samples/vfio-mdev/mtty.c
> > index 6b633a4ea333..e9c52e1f97a6 100644
> > --- a/samples/vfio-mdev/mtty.c
> > +++ b/samples/vfio-mdev/mtty.c
> > @@ -1446,6 +1446,7 @@ static int __init mtty_dev_init(void)
> >  	mtty_dev.vd_class = class_create(THIS_MODULE, MTTY_CLASS_NAME);
> >  
> >  	if (IS_ERR(mtty_dev.vd_class)) {
> > +		ret = PTR_ERR(mtty_dev.vd_class);
> >  		pr_err("Error: failed to register mtty_dev class\n");
> >  		goto failed1;
> >  	}
> > @@ -1458,7 +1459,8 @@ static int __init mtty_dev_init(void)
> >  	if (ret)
> >  		goto failed2;
> >  
> > -	if (mdev_register_device(&mtty_dev.dev, &mdev_fops) != 0)
> > +	ret = mdev_register_device(&mtty_dev.dev, &mdev_fops);
> > +	if (ret)
> >  		goto failed3;
> >  
> >  	mutex_init(&mdev_list_lock);
> > @@ -1467,11 +1469,9 @@ static int __init mtty_dev_init(void)
> >  	goto all_done;
> >  
> >  failed3:
> > -
> >  	device_unregister(&mtty_dev.dev);
> >  failed2:
> >  	class_destroy(mtty_dev.vd_class);
> > -
> >  failed1:
> >  	cdev_del(&mtty_dev.vd_cdev);
> >  	unregister_chrdev_region(mtty_dev.vd_devt, MINORMASK);
> >   

      reply	other threads:[~2017-01-04 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30 22:40 [PATCH] samples/vfio-mdev: don't return zero on failure paths in mtty_dev_init() Alexey Khoroshilov
2017-01-04 12:22 ` Kirti Wankhede
2017-01-04 15:30   ` Alex Williamson [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=20170104083041.312f4b94@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=dan.carpenter@oracle.com \
    --cc=khoroshilov@ispras.ru \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=ldv-project@linuxtesting.org \
    --cc=linux-kernel@vger.kernel.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