From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx4: fix buffer leakage on device close
Date: Wed, 28 Apr 2021 09:15:42 +0000 [thread overview]
Message-ID: <DM6PR12MB2748B7BD3FC02D4EC4D56A77CF409@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210417171414.6117-1-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Sent: Saturday, April 17, 2021 8:14 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Matan
> Azrad <matan@nvidia.com>; Ori Kam <orika@nvidia.com>
> Subject: [PATCH] net/mlx4: fix buffer leakage on device close
>
> The mlx4 PMD tracks the buffers (mbufs) for the packets being transmitted
> in the dedicated array named as "elts". The tx_burst routine frees the mbufs
> from this array once it needs to rearm the hardware descriptor and store the
> new mbuf, so it looks like as replacement mbuf pointer in the elts array.
>
> On the device stop mlx4 PMD freed only the part of elts according tail and
> head pointers, leaking the rest of buffers, remained in the elts array.
>
> Fixes: a2ce2121c01c ("net/mlx4: separate Tx configuration functions")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-04-28 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 17:14 Viacheslav Ovsiienko
2021-04-28 9:15 ` Raslan Darawsheh [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=DM6PR12MB2748B7BD3FC02D4EC4D56A77CF409@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@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).