From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Yunjian Wang <wangyunjian@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@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 RESEND] net/iavf: fix memoy leak in error path
Date: Thu, 14 Dec 2023 04:39:00 +0000 [thread overview]
Message-ID: <DM4PR11MB5994BD04B78CA5186CE8994CD78CA@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2be401c77779bdc38c8a79b006665ba623c6e2db.1701426993.git.wangyunjian@huawei.com>
> -----Original Message-----
> From: Yunjian Wang <wangyunjian@huawei.com>
> Sent: Thursday, December 14, 2023 9:46 AM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>; xudingke@huawei.com;
> jerry.lilijun@huawei.com; Yunjian Wang <wangyunjian@huawei.com>;
> stable@dpdk.org
> Subject: [PATCH RESEND] net/iavf: fix memoy leak in error path
>
> In iavf_security_ctx_create() allocated memory for the 'security_ctx', we should
> free it when memory malloc for the 'iavf_security_ctx' fails, otherwise it will lead
> to memory leak.
>
> Fixes: 6bc987ecb860 ("net/iavf: support IPsec inline crypto")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Thanks
Qi
prev parent reply other threads:[~2023-12-14 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:46 [PATCH 1/1] " Yunjian Wang
2023-12-14 1:45 ` [PATCH RESEND] " Yunjian Wang
2023-12-14 4:39 ` 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=DM4PR11MB5994BD04B78CA5186CE8994CD78CA@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jerry.lilijun@huawei.com \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.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).