From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Patrick MacArthur <patrick@patrickmacarthur.net>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vfio: fix file descriptor leak in multi-process applications
Date: Thu, 9 Feb 2017 11:41:21 +0000 [thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E45123697821E7143@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <20170126230521.28314-1-patrick@patrickmacarthur.net>
> -----Original Message-----
> From: Patrick MacArthur [mailto:patrick@patrickmacarthur.net]
> Sent: Thursday, January 26, 2017 11:05 PM
> To: dev@dpdk.org; Burakov, Anatoly <anatoly.burakov@intel.com>
> Cc: Patrick MacArthur <patrick@patrickmacarthur.net>
> Subject: [PATCH] vfio: fix file descriptor leak in multi-process applications
>
> When a secondary process wants access to the VFIO container file descriptor,
> the primary process calls vfio_get_container_fd() which always opens an
> entirely new file descriptor on /dev/vfio/vfio.
> However, once the file descriptor has been passed to the subprocess, it is
> effectively duplicated, meaning that the copy of the file descriptor in the
> primary process is no longer needed. However, the primary process does
> not close the duplicate fd, which results in a resource leak.
>
> This can be reproduced by starting a primary process with a small
> RLIMIT_NOFILE limit configured to use VFIO for at least one device, and
> repeatedly launching secondary processes until the file descriptor limit is
> exceeded.
>
> Fix the resource leak by closing the local vfio container file descriptor after
> passing it to the secondary process.
>
> Fixes: 2f4adfad0a69 ("vfio: add multiprocess support")
> Signed-off-by: Patrick MacArthur <patrick@patrickmacarthur.net>
> ---
> lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
> b/lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
> index 00cf919b64d0..fb4a2f84b180 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_vfio_mp_sync.c
> @@ -301,6 +301,7 @@ vfio_mp_sync_thread(void __rte_unused * arg)
> vfio_mp_sync_send_request(conn_sock,
> SOCKET_ERR);
> else
> vfio_mp_sync_send_fd(conn_sock, fd);
> + close(fd);
> break;
> case SOCKET_REQ_GROUP:
> /* wait for group number */
> --
> 2.9.3
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
next prev parent reply other threads:[~2017-02-09 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 23:05 Patrick MacArthur
2017-02-09 11:41 ` Burakov, Anatoly [this message]
2017-02-09 17:36 ` Thomas Monjalon
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=C6ECDF3AB251BE4894318F4E45123697821E7143@IRSMSX109.ger.corp.intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=patrick@patrickmacarthur.net \
/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).