All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: maorg@nvidia.com, linux-rdma@vger.kernel.org,
	Saeed Mahameed <saeedm@nvidia.com>,
	linux-netdev <netdev@vger.kernel.org>
Subject: Re: [bug report] net/mlx5: Add direct rule fs_cmd implementation
Date: Tue, 24 May 2022 16:01:19 +0300	[thread overview]
Message-ID: <YozXHxO85GpT+5GK@unreal> (raw)
In-Reply-To: <YnvAxF0JO7E0fZvO@kili>

On Wed, May 11, 2022 at 04:57:24PM +0300, Dan Carpenter wrote:
> [ I was reviewing old use after free warnings and stumbled across this
>   one which still needs fixing - dan ]
> 
> Hello Maor Gottlieb,
> 
> The patch 6a48faeeca10: "net/mlx5: Add direct rule fs_cmd
> implementation" from Aug 20, 2019, leads to the following Smatch
> static checker warning:
> 
> 	drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c:53 set_miss_action()
> 	warn: 'action' was already freed.
> 
> drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c
>     28 static int set_miss_action(struct mlx5_flow_root_namespace *ns,
>     29                            struct mlx5_flow_table *ft,
>     30                            struct mlx5_flow_table *next_ft)
>     31 {
>     32         struct mlx5dr_action *old_miss_action;
>     33         struct mlx5dr_action *action = NULL;
>     34         struct mlx5dr_table *next_tbl;
>     35         int err;
>     36 
>     37         next_tbl = next_ft ? next_ft->fs_dr_table.dr_table : NULL;
>     38         if (next_tbl) {
>     39                 action = mlx5dr_action_create_dest_table(next_tbl);
>     40                 if (!action)
>     41                         return -EINVAL;
>     42         }
>     43         old_miss_action = ft->fs_dr_table.miss_action;
>     44         err = mlx5dr_table_set_miss_action(ft->fs_dr_table.dr_table, action);
>     45         if (err && action) {
>     46                 err = mlx5dr_action_destroy(action);
>     47                 if (err) {
>     48                         action = NULL;
>     49                         mlx5_core_err(ns->dev, "Failed to destroy action (%d)\n",
>     50                                       err);
>     51                 }
> 
> If "err" is zero then "action" is freed.
> 
>     52         }
> --> 53         ft->fs_dr_table.miss_action = action;
>                                              ^^^^^^
> Use after free.

Thanks for the report.
https://lore.kernel.org/netdev/7fe70bbb120422cc71e6b018531954d58ea2e61e.1653397057.git.leonro@nvidia.com/T/#u

> 
>     54         if (old_miss_action) {
>     55                 err = mlx5dr_action_destroy(old_miss_action);
>     56                 if (err)
>     57                         mlx5_core_err(ns->dev, "Failed to destroy action (%d)\n",
>     58                                       err);
>     59         }
>     60 
>     61         return err;
>     62 }
> 
> regards,
> dan carpenter

  reply	other threads:[~2022-05-24 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 13:57 [bug report] net/mlx5: Add direct rule fs_cmd implementation Dan Carpenter
2022-05-24 13:01 ` Leon Romanovsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-05  9:08 Dan Carpenter

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=YozXHxO85GpT+5GK@unreal \
    --to=leon@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maorg@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.