patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>,
	Qiming Chen <chenqiming_huawei@163.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v3] net/ixgbe: fix mbuf leak
Date: Mon, 6 Sep 2021 01:45:06 +0000	[thread overview]
Message-ID: <4a45f9ecdb0544d5af3ed22d8a98c2bd@intel.com> (raw)
In-Reply-To: <BN8PR11MB3795CD2173A324592D4F8D6FF7D29@BN8PR11MB3795.namprd11.prod.outlook.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Wang, Haiyue
> Sent: Monday, September 6, 2021 9:22 AM
> To: Qiming Chen <chenqiming_huawei@163.com>; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3] net/ixgbe: fix mbuf leak
> 
> > -----Original Message-----
> > From: Qiming Chen <chenqiming_huawei@163.com>
> > Sent: Wednesday, September 1, 2021 15:23
> > To: dev@dpdk.org
> > Cc: Wang, Haiyue <haiyue.wang@intel.com>; Qiming Chen
> > <chenqiming_huawei@163.com>; stable@dpdk.org
> > Subject: [PATCH v3] net/ixgbe: fix mbuf leak
> >
> > A local test found that repeated port start and stop operations during
> > the continuous SSE vector bufflist receiving process will cause the
> > mbuf resource to run out. The final positioning is when the port is
> > stopped, the mbuf of the pkt_first_seg pointer is not released. Resources
> leak.
> > The patch scheme is to judge whether the pointer is empty when the
> > port is stopped, and release the corresponding mbuf if it is not empty.
> >
> > Fixes: af75078fece3 ("first public release")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Qiming Chen <chenqiming_huawei@163.com>
> > ---
> > v2:
> >   Sync to stable@dpdk.org
> > v3:
> >   Modify fixes commit
> > ---
> >  drivers/net/ixgbe/ixgbe_rxtx.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> 
> Acked-by: Haiyue Wang <haiyue.wang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi
> 
> 
> >
> > --
> > 2.30.1.windows.1


      reply	other threads:[~2021-09-06  1:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210831032805.5520-1-chenqiming_huawei@163.com>
2021-08-31  8:03 ` [dpdk-stable] [PATCH v2] " Qiming Chen
2021-08-31  8:06 ` Qiming Chen
2021-08-31 10:00   ` [dpdk-stable] [dpdk-dev] " Kevin Traynor
2021-09-01  1:50     ` Qiming Chen
2021-09-01  3:17       ` Wang, Haiyue
2021-09-01  7:22   ` [dpdk-stable] [PATCH v3] " Qiming Chen
2021-09-06  1:22     ` Wang, Haiyue
2021-09-06  1:45       ` Zhang, Qi Z [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=4a45f9ecdb0544d5af3ed22d8a98c2bd@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=chenqiming_huawei@163.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.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).