From: Saeed Mahameed <saeedm@nvidia.com>
To: "dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
Ariel Levkovich <lariel@nvidia.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Roi Dayan" <roid@nvidia.com>,
Ariel Levkovich <lariel@nvidia.com>,
"leon@kernel.org" <leon@kernel.org>
Subject: Re: [PATCH 1/2 net-next] net/mlx5e: TC: Fix IS_ERR() vs NULL checks
Date: Tue, 16 Feb 2021 21:37:51 +0000 [thread overview]
Message-ID: <90552f255570173e43948c058185c6c60c2fd855.camel@nvidia.com> (raw)
Message-ID: <20210216213751.5tt07PNyjEUl78aN582_w038wyczhwBf2bF-XIwmyS8@z> (raw)
In-Reply-To: <20210215083050.GA2222@kadam>
On Mon, 2021-02-15 at 11:30 +0300, Dan Carpenter wrote:
> On Mon, Sep 28, 2020 at 06:31:04PM +0000, Ariel Levkovich wrote:
> > On Sep 28, 2020, at 13:42, Dan Carpenter <dan.carpenter@oracle.com>
> > wrote:
> > >
> > > The mlx5_tc_ct_init() function doesn't return error pointers it
> > > returns
> > > NULL. Also we need to set the error codes on this path.
> > >
> > > Fixes: aedd133d17bc ("net/mlx5e: Support CT offload for tc nic
> > > flows")
> > > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > > ---
> > > drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 8 ++++++--
> > > 1 file changed, 6 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
> > > b/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
> > > index 104b1c339de0..438fbcf478d1 100644
> > > --- a/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
> > > +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
> > > @@ -5224,8 +5224,10 @@ int mlx5e_tc_nic_init(struct mlx5e_priv
> > > *priv)
> > >
> > > tc->ct = mlx5_tc_ct_init(priv, tc->chains, &priv-
> > > >fs.tc.mod_hdr,
> > > MLX5_FLOW_NAMESPACE_KERNEL);
> > > - if (IS_ERR(tc->ct))
> > > + if (!tc->ct) {
> > > + err = -ENOMEM;
> > > goto err_ct;
> > > + }
> >
> > Hi Dan,
> > That was implement like that on purpose. If mlx5_tc_init_ct returns
> > NULL it means the device doesn’t support CT offload which can
> > happen with older devices or old FW on the devices.
> > However, in this case we want to continue with the rest of the Tc
> > initialization because we can still support other TC offloads. No
> > need to fail the entire TC init in this case. Only if
> > mlx5_tc_init_ct return err_ptr that means the tc init failed not
> > because of lack of support but due to a real error and only then we
> > want to fail the rest of the tc init.
> >
> > Your change will break compatibility for devices/FW versions that
> > don’t have CT offload support.
> >
>
> When we have a function like this which is optional then returning
> NULL
> is a special kind of success as you say. Returning NULL should not
> generate a warning message. At the same time, if the user enables
> the
> option and the code fails because we are low on memory then returning
> an
> error pointer is the correct behavior. Just because the feature is
> optional does not mean we should ignore what the user told us to do.
>
> This code never returns error pointers. It always returns
> NULL/success
> when an allocation fails. That triggers the first static checker
> warning from last year. Now Smatch is complaining about a new static
> checker warning:
>
> drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:4754
> mlx5e_tc_esw_init() warn: missing error code here? 'IS_ERR()' failed.
> 'err' = '0'
>
> 4708 int mlx5e_tc_esw_init(struct rhashtable *tc_ht)
> 4709 {
> 4710 const size_t sz_enc_opts = sizeof(struct
> tunnel_match_enc_opts);
> 4711 struct mlx5_rep_uplink_priv *uplink_priv;
> 4712 struct mlx5e_rep_priv *rpriv;
> 4713 struct mapping_ctx *mapping;
> 4714 struct mlx5_eswitch *esw;
> 4715 struct mlx5e_priv *priv;
> 4716 int err = 0;
> 4717
> 4718 uplink_priv = container_of(tc_ht, struct
> mlx5_rep_uplink_priv, tc_ht);
> 4719 rpriv = container_of(uplink_priv, struct
> mlx5e_rep_priv, uplink_priv);
> 4720 priv = netdev_priv(rpriv->netdev);
> 4721 esw = priv->mdev->priv.eswitch;
> 4722
> 4723 uplink_priv->ct_priv =
> mlx5_tc_ct_init(netdev_priv(priv->netdev),
> 4724
> esw_chains(esw),
> 4725 &esw-
> >offloads.mod_hdr,
> 4726
> MLX5_FLOW_NAMESPACE_FDB);
> 4727 if (IS_ERR(uplink_priv->ct_priv))
> 4728 goto err_ct;
>
The driver is designed to tolerated failure in mlx5_tc_ct_init and is
supposed to continue here and not abort with return 0..
so either return proper errno or continue initializing, the code
currently has a bug.
Thanks Dan for pointing that out.
> If mlx5_tc_ct_init() fails, which it should do if kmalloc() fails but
> currently it does not, then the error should be propagated all the
> way
> back. So this code should preserve the error code instead of
> returning
> success.
>
> 4729
> 4730 mapping = mapping_create(sizeof(struct
> tunnel_match_key),
> 4731 TUNNEL_INFO_BITS_MASK,
> true);
>
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2021-02-16 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 17:41 [PATCH 1/2 net-next] net/mlx5e: TC: Fix IS_ERR() vs NULL checks Dan Carpenter
2020-09-28 17:42 ` [PATCH 2/2 net-next] net/mlx5e: TC: Fix potential Oops in mlx5e_tc_unoffload_from_slow_path() Dan Carpenter
2020-09-28 18:31 ` [PATCH 1/2 net-next] net/mlx5e: TC: Fix IS_ERR() vs NULL checks Ariel Levkovich
2020-09-28 18:51 ` Dan Carpenter
2021-02-15 8:30 ` Dan Carpenter
2021-02-16 21:37 ` Saeed Mahameed [this message]
2021-02-16 21:37 ` 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=90552f255570173e43948c058185c6c60c2fd855.camel@nvidia.com \
--to=saeedm@nvidia.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=lariel@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roid@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).