From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Yunjian Wang <wangyunjian@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"Wu, Wenjun1" <wenjun1.wu@intel.com>,
"xudingke@huawei.com" <xudingke@huawei.com>,
"jerry.lilijun@huawei.com" <jerry.lilijun@huawei.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2 RESEND] net/ixgbe: fix memoy leak after device init failure
Date: Mon, 18 Dec 2023 05:13:09 +0000 [thread overview]
Message-ID: <DM4PR11MB5994B41F12C6F6DE3059090BD790A@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5a8a0a3064089e63790d874631e4fb6ab160f17d.1702535665.git.wangyunjian@huawei.com>
> -----Original Message-----
> From: Yunjian Wang <wangyunjian@huawei.com>
> Sent: Monday, December 18, 2023 11:08 AM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Yang, Qiming <qiming.yang@intel.com>;
> Wu, Wenjun1 <wenjun1.wu@intel.com>; xudingke@huawei.com;
> jerry.lilijun@huawei.com; Yunjian Wang <wangyunjian@huawei.com>;
> stable@dpdk.org
> Subject: [PATCH v2 RESEND] net/ixgbe: fix memoy leak after device init failure
>
> In ixgbe_ipsec_ctx_create() allocated memory for the 'security_ctx', we should
> free it when errors occur, otherwise it will lead to memory leak.
>
> Fixes: 9a0752f498d2 ("net/ixgbe: enable inline IPsec")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2023-12-18 5:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:47 [PATCH 1/1] " Yunjian Wang
2023-12-14 1:46 ` [PATCH RESEND] " Yunjian Wang
2023-12-14 6:44 ` [PATCH v2] " Yunjian Wang
2023-12-18 3:07 ` [PATCH v2 RESEND] " Yunjian Wang
2023-12-18 5:13 ` 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=DM4PR11MB5994B41F12C6F6DE3059090BD790A@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jerry.lilijun@huawei.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.com \
--cc=wenjun1.wu@intel.com \
--cc=xudingke@huawei.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).