[lkml]   [2020]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/2] gpio: gpio-grgpio: fix possible sleep-in-atomic-context bugs in grgpio_irq_map/unmap()
On Wed, Dec 18, 2019 at 2:26 PM Jia-Ju Bai <> 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 <>

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

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?

Linus Walleij

 \ /
  Last update: 2020-01-07 10:38    [W:0.325 / U:1.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site