patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: abhishek.sachan@altran.com, linville@tuxdriver.com
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 18.11] net/af_packet: fix for stale sockets
Date: Fri, 23 Aug 2019 17:36:02 +0100	[thread overview]
Message-ID: <8cc9eb9d-906e-b746-059a-e847317866dc@redhat.com> (raw)
In-Reply-To: <1566220460-6324-1-git-send-email-abhishek.sachan@altran.com>

On 19/08/2019 14:14, abhishek.sachan@altran.com wrote:
> From: abhishek sachan <abhishek.sachan@altran.com>
> 
> af_packet driver is leaving stale socket after device is removed.
> Ring buffers are memory mapped when device is added using rte_dev_probe.
> There is no corresponding munmap call when device is removed/closed.
> This commit fixes the issue by calling munmap
> from rte_pmd_af_packet_remove().
> 
> Bugzilla ID: 339
> 

Thank you for the backport. I also see the patch on the ML for master -
will pick up for stable after it is merged into master.

Btw, if a patch on master has the right Fixes:/Cc:stable tags and
applies reasonably cleanly to stable, then it will be picked up for
stables as part of the normal process. Just fyi as it might save you
some effort sometime.

thanks,
Kevin.

> Signed-off-by: abhishek sachan <abhishek.sachan@altran.com>
> Reviewed-by: John W. Linville <linville@redhat.com>
> ---
>  drivers/net/af_packet/rte_eth_af_packet.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/net/af_packet/rte_eth_af_packet.c b/drivers/net/af_packet/rte_eth_af_packet.c
> index 264cfc0..657ad85 100644
> --- a/drivers/net/af_packet/rte_eth_af_packet.c
> +++ b/drivers/net/af_packet/rte_eth_af_packet.c
> @@ -972,6 +972,7 @@ rte_pmd_af_packet_remove(struct rte_vdev_device *dev)
>  {
>  	struct rte_eth_dev *eth_dev = NULL;
>  	struct pmd_internals *internals;
> +	struct tpacket_req *req;
>  	unsigned q;
>  
>  	PMD_LOG(INFO, "Closing AF_PACKET ethdev on numa socket %u",
> @@ -992,7 +993,10 @@ rte_pmd_af_packet_remove(struct rte_vdev_device *dev)
>  		return rte_eth_dev_release_port(eth_dev);
>  
>  	internals = eth_dev->data->dev_private;
> +	req = &internals->req;
>  	for (q = 0; q < internals->nb_queues; q++) {
> +		munmap(internals->rx_queue[q].map,
> +			2 * req->tp_block_size * req->tp_block_nr);
>  		rte_free(internals->rx_queue[q].rd);
>  		rte_free(internals->tx_queue[q].rd);
>  	}
> 


      parent reply	other threads:[~2019-08-23 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 13:14 abhishek.sachan
2019-08-19 18:35 ` John W. Linville
2019-08-23 16:36 ` Kevin Traynor [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=8cc9eb9d-906e-b746-059a-e847317866dc@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=abhishek.sachan@altran.com \
    --cc=linville@tuxdriver.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).