From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
David Marchand <david.marchand@redhat.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
Xiaolong Ye <xiaolong.ye@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Wang, Ying A" <ying.a.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/ice: fix memzone leak when device init failed
Date: Sun, 29 Aug 2021 11:01:47 +0000 [thread overview]
Message-ID: <ebfd6aafee7b47578a1f915b632302db@intel.com> (raw)
In-Reply-To: <20210813062154.62985-1-haiyue.wang@intel.com>
> -----Original Message-----
> From: Wang, Haiyue <haiyue.wang@intel.com>
> Sent: Friday, August 13, 2021 2:22 PM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Wang, Haiyue
> <haiyue.wang@intel.com>; stable@dpdk.org; David Marchand
> <david.marchand@redhat.com>; Yang, Qiming <qiming.yang@intel.com>;
> Xiaolong Ye <xiaolong.ye@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Wang, Ying A <ying.a.wang@intel.com>
> Subject: [PATCH v1] net/ice: fix memzone leak when device init failed
>
> When flow engine initialization or FXP resource reset failed, it needs to free the
> memory zone and unregister the interrupt callback.
>
> Bugzilla ID: 752
> Fixes: 84dc7a95a2d3 ("net/ice: enable flow director engine")
> Fixes: 7615a6895009 ("net/ice: rework for generic flow enabling")
> Fixes: 7edc7158d771 ("net/ice: cleanup RSS/FDIR profile on device init")
> Cc: stable@dpdk.org
>
> Reported-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2021-08-29 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 6:21 Haiyue Wang
2021-08-17 9:19 ` David Marchand
2021-08-18 0:46 ` Wang, Haiyue
2021-08-18 7:07 ` David Marchand
2021-08-29 11:01 ` 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=ebfd6aafee7b47578a1f915b632302db@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=xiaolong.ye@intel.com \
--cc=ying.a.wang@intel.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).