aboutsummaryrefslogtreecommitdiff
path: root/include/linux/blkpg.h
diff options
context:
space:
mode:
authorGravatar Shreeya Patel <shreeya.patel@collabora.com> 2022-03-21 19:02:41 +0530
committerGravatar Bartosz Golaszewski <brgl@bgdev.pl> 2022-04-04 14:41:34 +0200
commit5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 (patch)
treea32186986097a33e9836e207409aacdf72e5c348 /include/linux/blkpg.h
parentLinux 5.18-rc1 (diff)
downloadlinux-5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320.tar.gz
linux-5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320.tar.bz2
linux-5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320.zip
gpio: Restrict usage of GPIO chip irq members before initialization
GPIO chip irq members are exposed before they could be completely initialized and this leads to race conditions. One such issue was observed for the gc->irq.domain variable which was accessed through the I2C interface in gpiochip_to_irq() before it could be initialized by gpiochip_add_irqchip(). This resulted in Kernel NULL pointer dereference. Following are the logs for reference :- kernel: Call Trace: kernel: gpiod_to_irq+0x53/0x70 kernel: acpi_dev_gpio_irq_get_by+0x113/0x1f0 kernel: i2c_acpi_get_irq+0xc0/0xd0 kernel: i2c_device_probe+0x28a/0x2a0 kernel: really_probe+0xf2/0x460 kernel: RIP: 0010:gpiochip_to_irq+0x47/0xc0 To avoid such scenarios, restrict usage of GPIO chip irq members before they are completely initialized. Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com> Cc: stable@vger.kernel.org Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
Diffstat (limited to 'include/linux/blkpg.h')
0 files changed, 0 insertions, 0 deletions