public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mark Gross <markgross@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Vadim Pasternak <vadimp@nvidia.com>,
	Michael Shych <michaelsh@nvidia.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] platform/mellanox: mlxreg-lc: fix error code in mlxreg_lc_create_static_devices()
Date: Thu, 11 Nov 2021 10:39:50 +0300	[thread overview]
Message-ID: <20211111073949.GO2026@kadam> (raw)
In-Reply-To: <20211111073341.GN2001@kadam>

On Thu, Nov 11, 2021 at 10:33:41AM +0300, Dan Carpenter wrote:
> On Wed, Nov 10, 2021 at 02:31:47PM -0800, Mark Gross wrote:
> > On Wed, Nov 10, 2021 at 10:43:46AM +0300, Dan Carpenter wrote:
> > > This code should be using PTR_ERR() instead of IS_ERR().  And because
> > > it's using the wrong "dev->client" pointer, the IS_ERR() check will be
> > > false, meaning the function returns success.
> > > 
> > > Fixes: 62f9529b8d5c ("platform/mellanox: mlxreg-lc: Add initial support for Nvidia line card devices")
> > > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > > ---
> > >  drivers/platform/mellanox/mlxreg-lc.c | 5 +++--
> > >  1 file changed, 3 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/platform/mellanox/mlxreg-lc.c b/drivers/platform/mellanox/mlxreg-lc.c
> > > index 0b7f58feb701..c897a2f15840 100644
> > > --- a/drivers/platform/mellanox/mlxreg-lc.c
> > > +++ b/drivers/platform/mellanox/mlxreg-lc.c
> > > @@ -413,7 +413,7 @@ mlxreg_lc_create_static_devices(struct mlxreg_lc *mlxreg_lc, struct mlxreg_hotpl
> > >  				int size)
> > >  {
> > >  	struct mlxreg_hotplug_device *dev = devs;
> > > -	int i;
> > > +	int i, ret;
> > >  
> > >  	/* Create static I2C device feeding by auxiliary or main power. */
> > >  	for (i = 0; i < size; i++, dev++) {
> > > @@ -423,6 +423,7 @@ mlxreg_lc_create_static_devices(struct mlxreg_lc *mlxreg_lc, struct mlxreg_hotpl
> > >  				dev->brdinfo->type, dev->nr, dev->brdinfo->addr);
> > >  
> > >  			dev->adapter = NULL;
> > > +			ret = PTR_ERR(dev->client);
> > ret is only set on this error path.
> > can we get to the return without setting ret?
> > 
> 
> No.
> 
> :P
> 
> There two ways to read that question is if the patch introduces an
> uninitialized variable bug and I would be super embarrassed if I did
> something like that with all the QC scripts that I have to prevent it.
> The other way to read that question is if it's possible to not introduce
> the "ret" variable but instead figure it out at the end.  But the error
> code needs to be preserved at this point because we change change the
> "dev" pointer and set "dev->adapter" to NULL.
                         ^^^^^^^^^^^^
I meant "dev->client" not "dev->adapter".

regards,
dan carpenter

  reply	other threads:[~2021-11-11  7:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  7:43 [PATCH] platform/mellanox: mlxreg-lc: fix error code in mlxreg_lc_create_static_devices() Dan Carpenter
2021-11-10 10:27 ` Vadim Pasternak
2021-11-10 22:31 ` Mark Gross
2021-11-11  7:33   ` Dan Carpenter
2021-11-11  7:39     ` Dan Carpenter [this message]
2021-11-11  9:47 ` Hans de Goede

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=20211111073949.GO2026@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=hdegoede@redhat.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=michaelsh@nvidia.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=vadimp@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