[BUG] drivers/gpio: some possible sleep-in-atomic bugs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



According to drivers/gpio/gpio-grgpio.c, the kernel module may sleep under a spinlock.
The function call paths are:
grgpio_remove (acquire the spinlock)
  gpiochip_remove
    gpiochip_sysfs_unregister
      device_unregister --> may sleep
      mutex_lock --> may sleep

grgpio_remove (acquire the spinlock)
  gpiochip_remove
    gpiochip_sysfs_unregister
      gpiod_free
        __gpiod_free
          gpiod_unexport
            device_unregister --> may sleep
            mutex_lock --> may sleep

grgpio_remove (acquire the spinlock)
  irq_domain_remove
    mutex_lock --> may sleep

grgpio_irq_map (acquire the spinlock)
  request_irq --> may sleep

grgpio_irq_unmap (acquire the spinlock)
  free_irq --> may sleep


I do not find a good way to fix them, so I only report.
These possible bugs is found by my static analysis tool (DSAC) and checked by my code review.


Thanks,
Jia-Ju Bai
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux