From: Shreeya Patel <shreeya.patel@collabora.com>
To: linus.walleij@linaro.org, brgl@bgdev.pl, krisman@collabora.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, Shreeya Patel <shreeya.patel@collabora.com>
Subject: [PATCH] gpio: Initialize gc->irq.domain before setting gc->to_irq
Date: Tue, 9 Nov 2021 03:11:48 +0530 [thread overview]
Message-ID: <20211108214148.9724-1-shreeya.patel@collabora.com> (raw)
There is a race in registering of gc->irq.domain when
probing the I2C driver.
This sometimes leads to a Kernel NULL pointer dereference
in gpiochip_to_irq function which uses the domain variable.
To avoid this issue, set gc->to_irq after domain is
initialized. This will make sure whenever gpiochip_to_irq
is called, it has domain already initialized.
Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
---
Following is the NULL pointer dereference Oops 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: driver_probe_device+0xe8/0x160
kernel: ? driver_allows_async_probing+0x50/0x50
kernel: bus_for_each_drv+0x8f/0xd0
kernel: __device_attach_async_helper+0x9f/0xf0
kernel: async_run_entry_fn+0x2e/0x110
kernel: process_one_work+0x214/0x3e0
kernel: worker_thread+0x4d/0x3d0
kernel: ? process_one_work+0x3e0/0x3e0
kernel: kthread+0x133/0x150
kernel: ? kthread_associate_blkcg+0xc0/0xc0
kernel: ret_from_fork+0x22/0x30
kernel: CR2: 0000000000000028
kernel: ---[ end trace d0f5a7a0e0eb268f ]---
kernel: RIP: 0010:gpiochip_to_irq+0x47/0xc0
drivers/gpio/gpiolib.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index abfbf546d159..9a6f7c265a91 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1512,7 +1512,6 @@ static int gpiochip_add_irqchip(struct gpio_chip *gc,
if (gc->to_irq)
chip_warn(gc, "to_irq is redefined in %s and you shouldn't rely on it\n", __func__);
- gc->to_irq = gpiochip_to_irq;
gc->irq.default_type = type;
gc->irq.lock_key = lock_key;
gc->irq.request_key = request_key;
@@ -1533,6 +1532,8 @@ static int gpiochip_add_irqchip(struct gpio_chip *gc,
return -EINVAL;
}
+ gc->to_irq = gpiochip_to_irq;
+
if (gc->irq.parent_handler) {
for (i = 0; i < gc->irq.num_parents; i++) {
void *data;
--
2.30.2
next reply other threads:[~2021-11-08 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 21:41 Shreeya Patel [this message]
2021-11-09 13:48 ` [PATCH] gpio: Initialize gc->irq.domain before setting gc->to_irq Emil Velikov
2021-11-15 19:53 ` Gabriel Krisman Bertazi
2021-11-25 10:56 ` Shreeya Patel
2021-11-26 1:17 ` Linus Walleij
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=20211108214148.9724-1-shreeya.patel@collabora.com \
--to=shreeya.patel@collabora.com \
--cc=brgl@bgdev.pl \
--cc=kernel@collabora.com \
--cc=krisman@collabora.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