[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190401192115.3bc7ec4e.cohuck@redhat.com>
Date: Mon, 1 Apr 2019 19:21:15 +0200
From: Cornelia Huck <cohuck@...hat.com>
To: Parav Pandit <parav@...lanox.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
kwankhede@...dia.com, alex.williamson@...hat.com, cjia@...dia.com
Subject: Re: [PATCHv1 4/7] vfio/mdev: Avoid masking error code to EBUSY
On Tue, 26 Mar 2019 22:45:42 -0500
Parav Pandit <parav@...lanox.com> wrote:
> Instead of masking return error to -EBUSY, return actual error
> returned by the driver.
>
> Reviewed-by: Maxim Levitsky <mlevitsk@...hat.com>
> Signed-off-by: Parav Pandit <parav@...lanox.com>
> ---
> drivers/vfio/mdev/mdev_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/mdev/mdev_core.c b/drivers/vfio/mdev/mdev_core.c
> index 00ca613..836d319 100644
> --- a/drivers/vfio/mdev/mdev_core.c
> +++ b/drivers/vfio/mdev/mdev_core.c
> @@ -141,7 +141,7 @@ static int mdev_device_remove_ops(struct mdev_device *mdev, bool force_remove)
> */
> ret = parent->ops->remove(mdev);
> if (ret && !force_remove)
> - return -EBUSY;
> + return ret;
>
> sysfs_remove_groups(&mdev->dev.kobj, parent->ops->mdev_attr_groups);
> return 0;
Makes sense, even if no current ->remove callback returns anything
other than 0 or -EBUSY.
Reviewed-by: Cornelia Huck <cohuck@...hat.com>
Powered by blists - more mailing lists