From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Jim Harris <james.r.harris@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vfio: free mp_reply msgs in failure cases
Date: Tue, 20 Aug 2019 14:13:10 +0100 [thread overview]
Message-ID: <c36c5dcf-8363-ac7e-f884-ac111d73acfc@intel.com> (raw)
In-Reply-To: <156595762238.18723.10089009448135563310.stgit@jrharri1-skx>
On 16-Aug-19 1:13 PM, Jim Harris wrote:
> The code checks both rte_mp_request_sync() return
> code and that the number of messages in the reply
> equals 1. If rte_mp_request_sync() succeeds but
> there was more than one message, those messages
> would get leaked.
>
> Found via code review by Anatoly Burakov of patches
> that used the vhost code as a template for using
> rte_mp_request_sync().
>
> Signed-off-by: Jim Harris <james.r.harris@intel.com>
> ---
> lib/librte_eal/linux/eal/eal_vfio.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/lib/librte_eal/linux/eal/eal_vfio.c b/lib/librte_eal/linux/eal/eal_vfio.c
> index 501c74f23..d9541b122 100644
> --- a/lib/librte_eal/linux/eal/eal_vfio.c
> +++ b/lib/librte_eal/linux/eal/eal_vfio.c
> @@ -264,7 +264,7 @@ vfio_open_group_fd(int iommu_group_num)
> int vfio_group_fd;
> char filename[PATH_MAX];
> struct rte_mp_msg mp_req, *mp_rep;
> - struct rte_mp_reply mp_reply;
> + struct rte_mp_reply mp_reply = {0};
> struct timespec ts = {.tv_sec = 5, .tv_nsec = 0};
> struct vfio_mp_param *p = (struct vfio_mp_param *)mp_req.param;
>
> @@ -320,9 +320,9 @@ vfio_open_group_fd(int iommu_group_num)
> RTE_LOG(ERR, EAL, " bad VFIO group fd\n");
> vfio_group_fd = 0;
> }
> - free(mp_reply.msgs);
> }
>
> + free(mp_reply.msgs);
That's not quite correct. This fixes the problem of missing free() when
nb_received mismatches, but this /adds/ a problem of doing an
unnecessary free() when rte_mp_request_sync() returns -1. Same for other
places, i believe.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-08-20 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 12:13 Jim Harris
2019-08-20 13:13 ` Burakov, Anatoly [this message]
2019-08-20 13:16 ` Harris, James R
2019-08-20 13:22 ` Burakov, Anatoly
2019-10-14 11:17 ` David Marchand
2019-10-14 13:49 ` Harris, James R
2019-10-14 14:47 ` David Marchand
2019-10-14 14:50 ` Harris, James R
2019-10-15 18:38 ` David Marchand
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=c36c5dcf-8363-ac7e-f884-ac111d73acfc@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=james.r.harris@intel.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;
as well as URLs for NNTP newsgroup(s).