From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
"chenqiming_huawei@163.com" <chenqiming_huawei@163.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix mbuf leak
Date: Thu, 16 Sep 2021 17:16:40 +0100 [thread overview]
Message-ID: <6d42ca86-2eaa-98e3-427b-6e2e637eb06d@intel.com> (raw)
In-Reply-To: <f25a273560b247a28ffbad399dd88df7@intel.com>
On 9/13/2021 3:29 AM, Zhang, Qi Z wrote:
>
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of
>> chenqiming_huawei@163.com
>> Sent: Monday, August 23, 2021 9:51 AM
>> To: dev@dpdk.org
>> Cc: Xing, Beilei <beilei.xing@intel.com>; Qiming Chen
>> <chenqiming_huawei@163.com>; stable@dpdk.org
>> Subject: [dpdk-dev] [PATCH] net/i40e: fix mbuf leak
>>
>> From: Qiming Chen <chenqiming_huawei@163.com>
>>
>> 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 lead.
s/lead/leak/
Will update on next-net
>> 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: 5c9222058df7 ("i40e: move to drivers/net/")
>
> Fixes: 4861cde46116 ("i40e: new poll mode driver")
>
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Qiming Chen <chenqiming_huawei@163.com>
>
> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
>
> Applied to dpdk-next-net-intel.
>
> Thanks
> Qi
>
>
prev parent reply other threads:[~2021-09-16 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 1:50 chenqiming_huawei
2021-09-13 2:29 ` Zhang, Qi Z
2021-09-16 16:16 ` Ferruh Yigit [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=6d42ca86-2eaa-98e3-427b-6e2e637eb06d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=chenqiming_huawei@163.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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).