On Wed, Dec 18, 2019 at 2:26 PM Jia-Ju Bai <[email protected]> wrote:
> The driver may sleep while holding a spinlock.
> The function call path (from bottom to top) in Linux 4.19 is:
>
> drivers/gpio/gpio-grgpio.c, 261:
> request_irq in grgpio_irq_map
> drivers/gpio/gpio-grgpio.c, 255:
> _raw_spin_lock_irqsave in grgpio_irq_map
>
> drivers/gpio/gpio-grgpio.c, 318:
> free_irq in grgpio_irq_unmap
> drivers/gpio/gpio-grgpio.c, 299:
> _raw_spin_lock_irqsave in grgpio_irq_unmap
>
> request_irq() and free_irq() can sleep at runtime.
>
> To fix these bugs, request_irq() and free_irq() are called without
> holding the spinlock.
>
> These bugs are found by a static analysis tool STCheck written by myself.
>
> Signed-off-by: Jia-Ju Bai <[email protected]>
I suppose this is correct, so patch applied.
However there is a deeper problem, this code was added by Andreas
Larsson in 2013 and at the time this was a hacky way to deal with
an interrupt that is actually hierarchical.
Since 2013 we have gained:
- Hierarchical interrupt controllers
- Hierarchical interrupt chip helpers in gpiolib
So this code really needs to be modernized using a hierarchical
irqchip.
See for example commit:
aa7d618ac65f ("gpio: ixp4xx: Convert to hierarchical GPIOLIB_IRQCHIP")
for an example.
Who is using grgpio these days and could work on fixing this up?
Yours,
Linus Walleij
On 2020-01-07 10:37, Linus Walleij wrote:
> However there is a deeper problem, this code was added by Andreas
> Larsson in 2013 and at the time this was a hacky way to deal with
> an interrupt that is actually hierarchical.
>
> Since 2013 we have gained:
> - Hierarchical interrupt controllers
> - Hierarchical interrupt chip helpers in gpiolib
>
> So this code really needs to be modernized using a hierarchical
> irqchip.
>
> See for example commit:
> aa7d618ac65f ("gpio: ixp4xx: Convert to hierarchical GPIOLIB_IRQCHIP")
> for an example.
>
> Who is using grgpio these days and could work on fixing this up?
I will put on my list to look into this. GRGPIO is used in all our
chips, and in most designs made by our customers.
The main hurdle with the interrupt handling in the current driver was to
both allow several lines to generate the same system interrupt and at
the same time make sure to not register any system interrupts for any
lines until the user actually requests it (as in the general case all
interrupts would be registered leading to clashes with interrupts that
cannot necessarily be shared). Hopefully, the hierarchical interrupt
controller and chip helper functionalities can cater for these requirements.
Best regards,
Andreas Larsson