From: Jonathan Cameron <jic23@kernel.org>
To: Salah Triki <salah.triki@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Wang Shuaijie" <wangshuaijie@awinic.com>
Subject: Re: [PATCH] iio: proximity: aw96103: Fix early return in IRQ handler loop
Date: Thu, 20 Aug 2026 02:49:09 +0100 [thread overview]
Message-ID: <20260820024909.307601c0@jic23-huawei> (raw)
In-Reply-To: <20260820024653.251ac6a9@jic23-huawei>
On Thu, 20 Aug 2026 02:46:53 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Wed, 19 Aug 2026 22:08:26 +0100
> Salah Triki <salah.triki@gmail.com> wrote:
>
> > When an unrecognized proximity status is encountered in aw96103_irq(),
> > the default case executes a return IRQ_HANDLED. Because this happens
> > inside the loop over the device's channels, any remaining channels are
> > left unhandled, causing missed events and stale IRQ status.
> >
> > Replace the return IRQ_HANDLED statement in the default case with
> > continue to ensure all channels are processed even if one has an
> > unexpected status value.
> >
> > Fixes: 07b241262dca ("iio: proximity: aw96103: Add support for aw96103/aw96105 proximity sensor")
> Hi Salah,
>
> Interesting little find.
>
> So usual question for a fix: Have you seen this in the wild, or is
> it code reading / tool found? I'm not against changing it but it
> is useful to know this for attaching different levels of importance
> to the bug and hence how fast we merge it. Please add a note on that
> to the commit message for v2 (though let it sit for a while for others
> to look at)
>
> Is there a path for this to happen short of corruption / broken /
> malicious device? If not, no fixes tag - it's hardening or a useabilty
> improvement rather than a bug fix
+CC Wang Shuaijie who wrote this one and may be able to provide
more insight into why it previously exited on this condition.
Jonathan
>
> Thanks
>
> Jonathan
>
> > Signed-off-by: Salah Triki <salah.triki@gmail.com>
> > ---
> > drivers/iio/proximity/aw96103.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/proximity/aw96103.c b/drivers/iio/proximity/aw96103.c
> > index 8fbb755dcae0..b1f36a51d56f 100644
> > --- a/drivers/iio/proximity/aw96103.c
> > +++ b/drivers/iio/proximity/aw96103.c
> > @@ -669,7 +669,7 @@ static irqreturn_t aw96103_irq(int irq, void *data)
> > iio_get_time_ns(indio_dev));
> > break;
> > default:
> > - return IRQ_HANDLED;
> > + continue;
> > }
> > aw96103->channels_arr[i].old_irq_status = curr_status;
> > }
>
>
prev parent reply other threads:[~2026-08-20 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 21:08 [PATCH] iio: proximity: aw96103: Fix early return in IRQ handler loop Salah Triki
2026-08-20 1:46 ` Jonathan Cameron
2026-08-20 1:49 ` Jonathan Cameron [this message]
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=20260820024909.307601c0@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=salah.triki@gmail.com \
--cc=wangshuaijie@awinic.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