From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: Qiming Chen <chenqiming_huawei@163.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] net/ixgbe: fix mac resourece leak
Date: Mon, 6 Sep 2021 01:25:07 +0000 [thread overview]
Message-ID: <BN8PR11MB37955F12A171E1BAC1A06D6FF7D29@BN8PR11MB3795.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210901071207.9379-1-chenqiming_huawei@163.com>
> -----Original Message-----
> From: Qiming Chen <chenqiming_huawei@163.com>
> Sent: Wednesday, September 1, 2021 15:12
> 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 mac resourece leak
>
> In the eth_ixgbevf_dev_init and eth_ixgbe_dev_init functions, memory is
> allocated for the MAC address, and the address is stored in the
> eth_dev->data->mac_addrs member variable. If the subsequent function is
> abnormal, you need to use the rte_free function to release the MAC
> address memory.
>
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
>
> Signed-off-by: Qiming Chen <chenqiming_huawei@163.com>
> ---
> v2:
> Clear coding style warning.
> v3:
> Modify fixes commit.
> ---
> drivers/net/ixgbe/ixgbe_ethdev.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
Acked-by: Haiyue Wang <haiyue.wang@intel.com>
>
> --
> 2.30.1.windows.1
next prev parent reply other threads:[~2021-09-06 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 13:57 [dpdk-dev] [PATCH] " Qiming Chen
2021-08-31 14:21 ` [dpdk-dev] [PATCH v2] " Qiming Chen
2021-09-01 6:25 ` Wang, Haiyue
2021-09-01 7:26 ` Qiming Chen
2021-09-01 7:12 ` [dpdk-dev] [PATCH v3] " Qiming Chen
2021-09-06 1:25 ` Wang, Haiyue [this message]
2021-09-06 1:42 ` Zhang, Qi Z
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=BN8PR11MB37955F12A171E1BAC1A06D6FF7D29@BN8PR11MB3795.namprd11.prod.outlook.com \
--to=haiyue.wang@intel.com \
--cc=chenqiming_huawei@163.com \
--cc=dev@dpdk.org \
--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).