From: Luca Boccassi <bluca@debian.org>
To: Ophir Munk <ophirmu@mellanox.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v1] net/mlx5: fix secondary process resource leakage
Date: Wed, 01 Aug 2018 11:07:16 +0100 [thread overview]
Message-ID: <1533118036.20916.56.camel@debian.org> (raw)
In-Reply-To: <1533076587-18997-1-git-send-email-ophirmu@mellanox.com>
On Tue, 2018-07-31 at 22:36 +0000, Ophir Munk wrote:
> When running testpmd with an mlx5 device and then executing at
> testpmd
> prompt in a raw: "port start all" followed by "port stop all"
> a new file named /var/tmp/net_mlx5_<socket num> is created as a
> result
> of creating a new unix domain socket (used for communication between
> the primary and secondary processes).
> When the new unix socket file is created the old unix socket file
> should
> have been removed. This commit fixes it by closing the old unix
> socket
> just before creating the new one in function mlx5_socket_init()
>
> Fixes: f8b9a3bad467 ("net/mlx5: install a socket to exchange a file
> descriptor")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
> ---
> drivers/net/mlx5/mlx5_socket.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/net/mlx5/mlx5_socket.c
> b/drivers/net/mlx5/mlx5_socket.c
> index 99297d5..a3a5229 100644
> --- a/drivers/net/mlx5/mlx5_socket.c
> +++ b/drivers/net/mlx5/mlx5_socket.c
> @@ -36,6 +36,12 @@
> int flags;
>
> /*
> + * Close the last socket that was used to communicate
> + * with the secondary process
> + */
> + if (priv->primary_socket)
> + mlx5_socket_uninit(dev);
> + /*
> * Initialise the socket to communicate with the secondary
> * process.
> */
Hi,
Has this (or a version of this) been merged in master? For which of the
stable releases is this for?
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-08-01 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 22:36 Ophir Munk
2018-08-01 10:07 ` Luca Boccassi [this message]
2018-08-01 10:18 ` Ophir Munk
2018-07-31 22:38 Ophir Munk
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=1533118036.20916.56.camel@debian.org \
--to=bluca@debian.org \
--cc=ophirmu@mellanox.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).