DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: "NBU-Contact-longli (EXTERNAL)" <longli@microsoft.com>,
	Matan Azrad <matan@nvidia.com>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Karanjot Singh <ksingh1@paloaltonetworks.com>
Subject: RE: [Patch v2] net/mlx4: fix verbs fd leak in the secondary process
Date: Thu, 7 Jul 2022 09:44:15 +0000	[thread overview]
Message-ID: <DM6PR12MB37537852B0E5144170FBE5E4DF839@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1657129733-12126-1-git-send-email-longli@linuxonhyperv.com>

> -----Original Message-----
> From: longli@linuxonhyperv.com <longli@linuxonhyperv.com>
> Sent: Wednesday, July 6, 2022 20:49
> To: Matan Azrad <matan@nvidia.com>; Ferruh Yigit <ferruh.yigit@xilinx.com>
> Cc: dev@dpdk.org; Karanjot Singh <ksingh1@paloaltonetworks.com>; NBU-
> Contact-longli (EXTERNAL) <longli@microsoft.com>
> Subject: [Patch v2] net/mlx4: fix verbs fd leak in the secondary process
> 
> From: Long Li <longli@microsoft.com>
> 
> FDs passed from rte_mp_msg are duplicated to the secondary process and need
> to be closed.
> 
> Fixes: 0203d33a10 ("net/mlx4: support secondary process")
> Signed-off-by: Long Li <longli@microsoft.com>
> ---
> Change in v2: handle error case where mlx4_proc_priv_init() might fail
>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>


  parent reply	other threads:[~2022-07-07  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 17:48 longli
2022-07-06 17:48 ` [Patch v2] net/mlx5: " longli
2022-07-07  9:43   ` Slava Ovsiienko
2022-08-14 13:50   ` Raslan Darawsheh
2022-07-07  9:44 ` Slava Ovsiienko [this message]
2022-08-14 13:50 ` [Patch v2] net/mlx4: " Raslan Darawsheh

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=DM6PR12MB37537852B0E5144170FBE5E4DF839@DM6PR12MB3753.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=ksingh1@paloaltonetworks.com \
    --cc=longli@microsoft.com \
    --cc=matan@nvidia.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).