netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wojciech Drewek <wojciech.drewek@intel.com>
To: Dust Li <dust.li@linux.alibaba.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Cruz Zhao <cruzzhao@linux.alibaba.com>,
	Tianchen Ding <dtcccc@linux.alibaba.com>
Subject: Re: [PATCH net] net/mlx5e: fix double free of encap_header
Date: Wed, 25 Oct 2023 11:06:25 +0200	[thread overview]
Message-ID: <5a89b15e-e4ca-4e06-9069-6f005c6884f2@intel.com> (raw)
In-Reply-To: <20231025032712.79026-1-dust.li@linux.alibaba.com>



On 25.10.2023 05:27, Dust Li wrote:
> When mlx5_packet_reformat_alloc() fails, the encap_header allocated in
> mlx5e_tc_tun_create_header_ipv4{6} will be released within it. However,
> e->encap_header is already set to the previously freed encap_header
> before mlx5_packet_reformat_alloc(). As a result, the later
> mlx5e_encap_put() will free e->encap_header again, causing a double free
> issue.
> 
> mlx5e_encap_put()
>     --> mlx5e_encap_dealloc()
>         --> kfree(e->encap_header)

nit: I think it should mlx5e_encap_put_locked not mlx5e_encap_put to be precise.

> 
> This happens when cmd: MLX5_CMD_OP_ALLOC_PACKET_REFORMAT_CONTEXT fail.
> 
> This patch fix it by not setting e->encap_header until
> mlx5_packet_reformat_alloc() success.
> 
> Fixes: d589e785baf5e("net/mlx5e: Allow concurrent creation of encap entries")
> Reported-by: Cruz Zhao <cruzzhao@linux.alibaba.com>
> Reported-by: Tianchen Ding <dtcccc@linux.alibaba.com>
> Signed-off-by: Dust Li <dust.li@linux.alibaba.com>
> ---

Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>

>  drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.c | 10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.c b/drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.c
> index 00a04fdd756f..8bca696b6658 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.c
> @@ -300,9 +300,6 @@ int mlx5e_tc_tun_create_header_ipv4(struct mlx5e_priv *priv,
>  	if (err)
>  		goto destroy_neigh_entry;
>  
> -	e->encap_size = ipv4_encap_size;
> -	e->encap_header = encap_header;
> -
>  	if (!(nud_state & NUD_VALID)) {
>  		neigh_event_send(attr.n, NULL);
>  		/* the encap entry will be made valid on neigh update event
> @@ -322,6 +319,8 @@ int mlx5e_tc_tun_create_header_ipv4(struct mlx5e_priv *priv,
>  		goto destroy_neigh_entry;
>  	}
>  
> +	e->encap_size = ipv4_encap_size;
> +	e->encap_header = encap_header;
>  	e->flags |= MLX5_ENCAP_ENTRY_VALID;
>  	mlx5e_rep_queue_neigh_stats_work(netdev_priv(attr.out_dev));
>  	mlx5e_route_lookup_ipv4_put(&attr);
> @@ -568,9 +567,6 @@ int mlx5e_tc_tun_create_header_ipv6(struct mlx5e_priv *priv,
>  	if (err)
>  		goto destroy_neigh_entry;
>  
> -	e->encap_size = ipv6_encap_size;
> -	e->encap_header = encap_header;
> -
>  	if (!(nud_state & NUD_VALID)) {
>  		neigh_event_send(attr.n, NULL);
>  		/* the encap entry will be made valid on neigh update event
> @@ -590,6 +586,8 @@ int mlx5e_tc_tun_create_header_ipv6(struct mlx5e_priv *priv,
>  		goto destroy_neigh_entry;
>  	}
>  
> +	e->encap_size = ipv6_encap_size;
> +	e->encap_header = encap_header;
>  	e->flags |= MLX5_ENCAP_ENTRY_VALID;
>  	mlx5e_rep_queue_neigh_stats_work(netdev_priv(attr.out_dev));
>  	mlx5e_route_lookup_ipv6_put(&attr);

  reply	other threads:[~2023-10-25  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  3:27 [PATCH net] net/mlx5e: fix double free of encap_header Dust Li
2023-10-25  9:06 ` Wojciech Drewek [this message]
2023-10-27  6:58   ` Dust Li
2023-10-26 23:00 ` Saeed Mahameed

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=5a89b15e-e4ca-4e06-9069-6f005c6884f2@intel.com \
    --to=wojciech.drewek@intel.com \
    --cc=cruzzhao@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=dtcccc@linux.alibaba.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.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).