public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Ethan Tidmore" <ethantidmore06@gmail.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 05/10] iio: light: gp2ap020a00f: Fix possible error swallow
Date: Mon, 23 Feb 2026 21:15:44 +0000	[thread overview]
Message-ID: <20260223211544.7eeb67c2@jic23-huawei> (raw)
In-Reply-To: <aZxCf3zD7m3nxaH5@smile.fi.intel.com>

On Mon, 23 Feb 2026 14:05:19 +0200
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> On Sun, Feb 22, 2026 at 09:40:15PM -0600, Ethan Tidmore wrote:
> > Move error check into for loop in gp2ap020a00f_buffer_postenable() and
> > gp2ap020a00f_buffer_predisable(), this fixes a possible error swallow.  
> 
> ...
> 
> > -	int i, err = 0;
> > +	int i, err;  
> 
> I believe we can't do that without introducing a 'default' case.

I agree. I'm a bit confused why LLVM at least isn't moaning about this.

Anyhow, I'm not sure why it defaulted to 0 previously...

diff --git a/drivers/iio/light/gp2ap020a00f.c b/drivers/iio/light/gp2ap020a00f.c
index d2156e133b75..64be9b8ca5e3 100644
--- a/drivers/iio/light/gp2ap020a00f.c
+++ b/drivers/iio/light/gp2ap020a00f.c
@@ -1365,6 +1365,9 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
                        err = gp2ap020a00f_exec_cmd(data,
                                        GP2AP020A00F_CMD_TRIGGER_PROX_EN);
                        break;
+               default:
+                       err = -EINVAL;
+                       break;
                }
                if (err)
                        return err;
@@ -1398,6 +1401,9 @@ static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
                        err = gp2ap020a00f_exec_cmd(data,
                                        GP2AP020A00F_CMD_TRIGGER_PROX_DIS);
                        break;
+               default:
+                       err = -EINVAL;
+                       break;
                }
                if (err)
                        return err;

Is the tweak I applied to resolve this.

Thanks,

Jonathan

> 
> >  	guard(mutex)(&data->lock);
> >  
> > @@ -1366,11 +1366,10 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
> >  					GP2AP020A00F_CMD_TRIGGER_PROX_EN);
> >  			break;
> >  		}
> > +		if (err)
> > +			return err;
> >  	}
> >  
> > -	if (err < 0)
> > -		return err;  
> 
> (Also you might want to mention dropping '< 0' for making the style consistent
>  taking into account that those functions won't return any positive values.)
> 
> >  	data->buffer = kmalloc(indio_dev->scan_bytes, GFP_KERNEL);
> >  	if (!data->buffer)
> >  		return -ENOMEM;
> > @@ -1381,7 +1380,7 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
> >  static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
> >  {
> >  	struct gp2ap020a00f_data *data = iio_priv(indio_dev);
> > -	int i, err = 0;
> > +	int i, err;  
> 
> Ditto.
> 
> >  	guard(mutex)(&data->lock);
> >  
> > @@ -1400,11 +1399,10 @@ static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
> >  					GP2AP020A00F_CMD_TRIGGER_PROX_DIS);
> >  			break;
> >  		}
> > +		if (err)
> > +			return err;
> >  	}
> >  
> > -	if (err)
> > -		return err;
> > -
> >  	kfree(data->buffer);
> >  	return 0;
> >  }  
> 


  reply	other threads:[~2026-02-23 21:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  3:40 [PATCH v5 00/10] General clean up and bug fixes Ethan Tidmore
2026-02-23  3:40 ` [PATCH v5 01/10] iio: light: gp2ap020a00f: simplify locking with guard() Ethan Tidmore
2026-02-23 11:54   ` Andy Shevchenko
2026-02-23  3:40 ` [PATCH v5 02/10] iio: light: gp2ap020a00f: correct return type to int Ethan Tidmore
2026-02-23  3:40 ` [PATCH v5 03/10] iio: light: gp2ap020a00f: Use correct types for 16-bit LE data Ethan Tidmore
2026-02-23  3:40 ` [PATCH v5 04/10] iio: light: gp2ap020a00f: Return directly from the switch cases Ethan Tidmore
2026-02-23 12:00   ` Andy Shevchenko
2026-02-23  3:40 ` [PATCH v5 05/10] iio: light: gp2ap020a00f: Fix possible error swallow Ethan Tidmore
2026-02-23 12:05   ` Andy Shevchenko
2026-02-23 21:15     ` Jonathan Cameron [this message]
2026-02-23  3:40 ` [PATCH v5 06/10] iio: light: gp2ap020a00f: Replace custom implementation of min() Ethan Tidmore
2026-02-23  3:40 ` [PATCH v5 07/10] iio: light: gp2ap020a00f: Use temporary variable for struct device Ethan Tidmore
2026-02-23  3:40 ` [PATCH v5 08/10] iio: light: gp2ap020a00f: Explicitly use string literal for driver name Ethan Tidmore
2026-02-23  3:40 ` [PATCH v5 09/10] iio: light: gp2ap020a00f: Remove trailing comma in termination entry Ethan Tidmore
2026-02-23  3:40 ` [PATCH v5 10/10] iio: light: gp2ap020a00f: Join some lines of code to be a single line Ethan Tidmore
2026-02-23 12:16 ` [PATCH v5 00/10] General clean up and bug fixes Andy Shevchenko
2026-02-23 12:17   ` Andy Shevchenko
2026-02-23 21:18     ` Jonathan Cameron
2026-02-24  9:45       ` Andy Shevchenko

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=20260223211544.7eeb67c2@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=ethantidmore06@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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