From: Stefano Garzarella <sgarzare@redhat.com>
To: Colin King <colin.king@canonical.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Eli Cohen <elic@nvidia.com>
Subject: Re: [PATCH][next] vpda: Fix memory leaks of msg on error return paths
Date: Mon, 25 Jan 2021 11:21:36 +0100 [thread overview]
Message-ID: <20210125102136.6e7dye5ucoe5qiw2@steredhat> (raw)
In-Reply-To: <20210122145235.209121-1-colin.king@canonical.com>
On Fri, Jan 22, 2021 at 02:52:35PM +0000, Colin King wrote:
>From: Colin Ian King <colin.king@canonical.com>
>
>There are two error return paths that neglect to free the allocated
>object msg that lead to memory leaks. Fix this by adding an error
>exit path that frees msg.
>
>Addresses-Coverity: ("Resource leak")
>Fixes: 39502d042a70 ("vdpa: Enable user to query vdpa device info")
>Signed-off-by: Colin Ian King <colin.king@canonical.com>
>---
> drivers/vdpa/vdpa.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
>index 9700a0adcca0..eb1f5a514103 100644
>--- a/drivers/vdpa/vdpa.c
>+++ b/drivers/vdpa/vdpa.c
>@@ -540,13 +540,15 @@ static int vdpa_nl_cmd_dev_get_doit(struct sk_buff *skb, struct genl_info *info)
> 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 err;
> }
> err = vdpa_dev_fill(vdev, msg, info->snd_portid, info->snd_seq, 0, info->extack);
> if (!err)
>@@ -554,6 +556,7 @@ static int vdpa_nl_cmd_dev_get_doit(struct sk_buff *skb, struct genl_info *info)
> put_device(dev);
> mutex_unlock(&vdpa_dev_mutex);
>
>+err:
> if (err)
> nlmsg_free(msg);
> return err;
The patch looks okay, but reviewing it I figure out that if
genlmsg_reply() returns an error, it also frees the sk_buff passed, so
IIUC calling nlmsg_free() when genlmsg_reply() fails should cause a
double free.
Maybe we should do something like this (not tested):
diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
index 9700a0adcca0..920afcb4aa75 100644
--- a/drivers/vdpa/vdpa.c
+++ b/drivers/vdpa/vdpa.c
@@ -538,24 +538,29 @@ 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_msg;
}
vdev = container_of(dev, struct vdpa_device, dev);
if (!vdev->mdev) {
- mutex_unlock(&vdpa_dev_mutex);
- put_device(dev);
- return -EINVAL;
+ err = -EINVAL;
+ goto err_dev;
}
err = vdpa_dev_fill(vdev, msg, info->snd_portid, info->snd_seq, 0, info->extack);
- if (!err)
- err = genlmsg_reply(msg, info);
+ if (err)
+ goto err_dev;
+
put_device(dev);
mutex_unlock(&vdpa_dev_mutex);
- if (err)
- nlmsg_free(msg);
+ return genlmsg_reply(msg, info);
+
+err_dev:
+ put_device(dev);
+err_msg:
+ mutex_unlock(&vdpa_dev_mutex);
+ nlmsg_free(msg);
return err;
}
Thanks,
Stefano
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2021-01-25 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 14:52 [PATCH][next] vpda: Fix memory leaks of msg on error return paths Colin King
2021-01-25 10:21 ` 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=20210125102136.6e7dye5ucoe5qiw2@steredhat \
--to=sgarzare@redhat.com \
--cc=colin.king@canonical.com \
--cc=elic@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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