From: Stefano Garzarella <sgarzare@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtualization@lists.linux-foundation.org, mst@redhat.com
Subject: Re: [PATCH linux-next v2] vdpa: Fix memory leak in error unwinding path
Date: Wed, 17 Feb 2021 09:20:28 +0100 [thread overview]
Message-ID: <20210217082028.6dsdydy4wavrl64g@steredhat> (raw)
In-Reply-To: <20210217060614.59561-1-parav@nvidia.com>
On Wed, Feb 17, 2021 at 08:06:14AM +0200, Parav Pandit wrote:
>When device get command fails to find the device or mdev,
>it skips to free the skb during error unwinding path.
>Fix it by freeing in error unwind path.
>While at it, make error unwind path more clear to avoid such errors.
>
>Fixes: a12a2f694ce8 ("vdpa: Enable user to query vdpa device info")
>Signed-off-by: Parav Pandit <parav@nvidia.com>
>---
>changelog:
>v1->v2:
> - Addressed Stefano's comment to make error unwind code more clear
>---
> drivers/vdpa/vdpa.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
>diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
>index 3d997b389345..da67f07e24fd 100644
>--- a/drivers/vdpa/vdpa.c
>+++ b/drivers/vdpa/vdpa.c
>@@ -538,22 +538,22 @@ static int vdpa_nl_cmd_dev_get_doit(struct sk_buff *skb, struct genl_info *info)
> mutex_lock(&vdpa_dev_mutex);
> dev = bus_find_device(&vdpa_bus, NULL, devname, vdpa_name_match);
> if (!dev) {
>- mutex_unlock(&vdpa_dev_mutex);
> NL_SET_ERR_MSG_MOD(info->extack, "device not found");
>- return -ENODEV;
>+ err = -ENODEV;
>+ goto err;
> }
> vdev = container_of(dev, struct vdpa_device, dev);
> if (!vdev->mdev) {
>- mutex_unlock(&vdpa_dev_mutex);
>- put_device(dev);
>- return -EINVAL;
>+ err = -EINVAL;
>+ goto mdev_err;
> }
> err = vdpa_dev_fill(vdev, msg, info->snd_portid, info->snd_seq, 0, info->extack);
> if (!err)
> err = genlmsg_reply(msg, info);
>+mdev_err:
> put_device(dev);
>+err:
> mutex_unlock(&vdpa_dev_mutex);
>-
> if (err)
> nlmsg_free(msg);
> return err;
>--
>2.26.2
>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2021-02-17 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 6:06 [PATCH linux-next v2] vdpa: Fix memory leak in error unwinding path Parav Pandit
2021-02-17 8:20 ` Stefano Garzarella [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=20210217082028.6dsdydy4wavrl64g@steredhat \
--to=sgarzare@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux-foundation.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