From: Marc Zyngier <maz@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
kernel-team@android.com
Subject: Re: [PATCH] gpio: pca953x: Survive spurious interrupts
Date: Wed, 07 Oct 2020 14:20:30 +0100 [thread overview]
Message-ID: <bab5b8d99b57710030955c3924c9fca5@kernel.org> (raw)
In-Reply-To: <CAHp75VdQixJStuVj_aMZ9PhkWXk4RoUa13wAMDj4KGwm2t9nFQ@mail.gmail.com>
On 2020-10-07 14:10, Andy Shevchenko wrote:
> On Wed, Oct 7, 2020 at 3:09 PM Marc Zyngier <maz@kernel.org> wrote:
>> On 2020-10-07 13:02, Andy Shevchenko wrote:
>> > On Wed, Oct 7, 2020 at 12:49 PM Linus Walleij
>> > <linus.walleij@linaro.org> wrote:
>> >> On Mon, Oct 5, 2020 at 4:02 PM Marc Zyngier <maz@kernel.org> wrote:
>> >>
>> >> > The pca953x driver never checks the result of irq_find_mapping(),
>> >> > which returns 0 when no mapping is found. When a spurious interrupt
>> >> > is delivered (which can happen under obscure circumstances), the
>> >> > kernel explodes as it still tries to handle the error code as
>> >> > a real interrupt.
>> >> >
>> >> > Handle this particular case and warn on spurious interrupts.
>> >> >
>> >> > Signed-off-by: Marc Zyngier <maz@kernel.org>
>> >
>> > Wait, doesn't actually [1] fix the reported issue?
>>
>> Not at all.
>>
>> > Marc, can you confirm this?
>> >
>> > [1]: e43c26e12dd4 ("gpio: pca953x: Fix uninitialized pending variable")
>>
>> Different bug, really. If an interrupt is *really* pending, and no
>> mapping established yet, feeding the result of irq_find_mapping() to
>> handle_nested_irq() will lead to a panic.
>
> I don't understand. We have plenty of drivers doing exactly the way
> without checking this returned code.
I'm sure we do. Most driver code is buggy as hell, but I don't see that
as a reason to cargo-cult the crap. The API is crystal clear that it can
return 0 for no mapping, and 0 isn't a valid interrupt.
> What circumstances makes the mapping be absent?
Other bugs in the system ([1]), spurious interrupts (which can *always*
happen).
> Shouldn't we rather change this:
>
> girq->handler = handle_simple_irq;
> to this:
> girq->handler = handle_bad_irq;
> ?
I don't understand what you are trying to achieve with that, apart from
maybe breaking the driver. The right way to handle spurious interrupts
is by telling the core code that the interrupt wasn't handled, and to
let
the spurious interrupt code do its magic.
M.
[1] https://lore.kernel.org/r/20201005111443.1390096-1-maz@kernel.org
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-10-07 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 14:02 [PATCH] gpio: pca953x: Survive spurious interrupts Marc Zyngier
2020-10-07 9:48 ` Linus Walleij
2020-10-07 12:02 ` Andy Shevchenko
2020-10-07 12:09 ` Marc Zyngier
2020-10-07 13:10 ` Andy Shevchenko
2020-10-07 13:20 ` Marc Zyngier [this message]
2020-10-07 14:03 ` Andy Shevchenko
2020-10-07 15:00 ` Marc Zyngier
2020-10-07 15:43 ` 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=bab5b8d99b57710030955c3924c9fca5@kernel.org \
--to=maz@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=kernel-team@android.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).