From: Simon Horman <simon.horman@corigine•com>
To: Zhengchao Shao <shaozhengchao@huawei•com>
Cc: netdev@vger•kernel.org, linux-rdma@vger•kernel.org,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, borisp@nvidia•com, saeedm@nvidia•com,
leon@kernel•org, raeds@nvidia•com, ehakim@nvidia•com,
liorna@nvidia•com, nathan@kernel•org, weiyongjun1@huawei•com,
yuehaibing@huawei•com
Subject: Re: [PATCH net] net/mlx5e: fix double free in macsec_fs_tx_create_crypto_table_groups
Date: Tue, 4 Jul 2023 18:04:03 +0100 [thread overview]
Message-ID: <ZKRRA7KPr9ymAdK1@corigine.com> (raw)
In-Reply-To: <20230704070640.368652-1-shaozhengchao@huawei.com>
On Tue, Jul 04, 2023 at 03:06:40PM +0800, Zhengchao Shao wrote:
> In function macsec_fs_tx_create_crypto_table_groups(), when the ft->g
> memory is successfully allocated but the 'in' memory fails to be
> allocated, the memory pointed to by ft->g is released once. And in function
> macsec_fs_tx_create(), macsec_fs_tx_destroy() is called to release the
> memory pointed to by ft->g again. This will cause double free problem.
>
> Fixes: e467b283ffd5 ("net/mlx5e: Add MACsec TX steering rules")
> Signed-off-by: Zhengchao Shao <shaozhengchao@huawei•com>
Reviewed-by: Simon Horman <simon.horman@corigine•com>
next prev parent reply other threads:[~2023-07-04 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 7:06 [PATCH net] net/mlx5e: fix double free in macsec_fs_tx_create_crypto_table_groups Zhengchao Shao
2023-07-04 17:04 ` Simon Horman [this message]
2023-07-05 5:39 ` Leon Romanovsky
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=ZKRRA7KPr9ymAdK1@corigine.com \
--to=simon.horman@corigine$(echo .)com \
--cc=borisp@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=ehakim@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=liorna@nvidia$(echo .)com \
--cc=nathan@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=raeds@nvidia$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=shaozhengchao@huawei$(echo .)com \
--cc=weiyongjun1@huawei$(echo .)com \
--cc=yuehaibing@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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