| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 27 Aug 2013 12:17:12 -0700
From: Tim Bird <tbird20d@...il.com>
To: grant.likely@...aro.org, linus.walleij@...aro.org,
linux-gpio@...r.kernel.org
CC: linux-kernel@...r.kernel.org, tbird20d@...il.com,
tim.bird@...ymobile.com
Subject: RFC: Bug in error handling in gpiolib.c
Hi all,
There appears to be a bug in the error handling in
drivers/gpi/gpiolib.c In certain error cases
desc_to_gpio() is called to get the gpio number
for an error message, but this may happen on code
paths where desc->chip is NULL. This causes a panic
on my system in gpiod_request(), as follows:
[ 4.838393] Unable to handle kernel NULL pointer dereference at virtual address 00000044
[ 4.846379] pgd = c0204000
[ 4.849041] [00000044] *pgd=00000000
[ 4.852572] Internal error: Oops: 5 [#1] PREEMPT ARM
[ 4.857470] CPU: 0 PID: 1 Comm: swapper Not tainted 3.11.0-rc1-00306-g0db7796-dirty #78
[ 4.865373] task: ef01fb80 ti: ef034000 task.ti: ef034000
[ 4.870703] PC is at gpiod_request+0x84/0x2c8
[ 4.874995] LR is at gpiod_request+0x84/0x2c8
[ 4.879293] pc : [<c03373c0>] lr : [<c03373c0>] psr: 40000093
[ 4.879293] sp : ef035e00 ip : 000008d0 fp : 00000000
[ 4.890631] r10: 00000000 r9 : ef07ee20 r8 : 40000013
[ 4.895788] r7 : ef034000 r6 : c0482c88 r5 : c0529b90 r4 : fffffdfb
[ 4.902232] r3 : 00000000 r2 : ef035d78 r1 : 00000000 r0 : 00000011
[ 4.908681] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 4.915982] Control: 10c5787d Table: 80204059 DAC: 00000015
[ 4.921652] Process swapper (pid: 1, stack limit = 0xef034230)
[ 4.927408] Stack: (0xef035e00 to 0xef036000)
[ 4.931711] 5e00: 00000000 ef07ee00 ef199880 ef19ae00 ef07ee20 00000001 ef19ae80 c036d0d0
[ 4.939789] 5e20: c0481694 c0482e38 ef07c440 00000035 ef07ee20 ef07ee20 c04f9298 ef07ee00
[ 4.947865] 5e40: 00000000 c052b6b8 00000000 c04ab224 00000000 c037ff84 ef07ee20 c04f9298
[ 4.955943] 5e60: c052b6b0 c03625c8 ef07c440 c04bbd4c ef07ee20 c04f9298 ef07ee54 ef19bdc0
[ 4.964019] 5e80: c04bbd4c c0362840 00000000 c04f9298 c03627b4 c0360c00 ef063318 ef07baf0
[ 4.972097] 5ea0: 00000000 c04f9298 c04f9884 c0361390 c0482e38 c0316f9c c04f9298 c04c021c
[ 4.980174] 5ec0: fa7e5603 00000000 c04bbd4c c0362e1c c04f9884 c04f9274 c04c021c fa7e5603
[ 4.988250] 5ee0: 00000000 c04bbd4c c04ab224 c0381160 00000000 00000006 c04c021c c04ab888
[ 4.996327] 5f00: 00000030 00000000 fa7e5603 00000000 c04ff100 40000013 c04d0e98 00000001
[ 5.004406] 5f20: c05339ff c04305dc 0000003c c0234950 ef035f5c c023ee94 c0483d94 c0494388
[ 5.012481] 5f40: 00000006 00000006 c04d0e8c 00000006 00000006 c04c021c c04c3428 c04ff140
[ 5.020558] 5f60: 0000003c c04c0228 c04ab224 c04aba64 00000006 00000006 c04ab224 ffffffff
[ 5.028635] 5f80: ef035f9c c023ed44 00000000 c041d20c 00000000 00000000 00000000 00000000
[ 5.036713] 5fa0: 00000000 c041d214 00000000 c020e298 00000000 00000000 00000000 00000000
[ 5.044790] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 5.052866] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 ffffffff ffffffff
[ 5.060961] [<c03373c0>] (gpiod_request+0x84/0x2c8) from [<c036d0d0>] (lc898300_probe+0x1c4/0x49c)
[ 5.069804] [<c036d0d0>] (lc898300_probe+0x1c4/0x49c) from [<c037ff84>] (i2c_device_probe+0x88/0xcc)
[ 5.078830] [<c037ff84>] (i2c_device_probe+0x88/0xcc) from [<c03625c8>] (driver_probe_device+0xe4/0x2d0)
[ 5.088192] [<c03625c8>] (driver_probe_device+0xe4/0x2d0) from [<c0362840>] (__driver_attach+0x8c/0x90)
[ 5.097470] [<c0362840>] (__driver_attach+0x8c/0x90) from [<c0360c00>] (bus_for_each_dev+0x54/0x88)
[ 5.106405] [<c0360c00>] (bus_for_each_dev+0x54/0x88) from [<c0361390>] (bus_add_driver+0xc8/0x22c)
[ 5.115342] [<c0361390>] (bus_add_driver+0xc8/0x22c) from [<c0362e1c>] (driver_register+0x78/0x14c)
[ 5.124282] [<c0362e1c>] (driver_register+0x78/0x14c) from [<c0381160>] (i2c_register_driver+0x2c/0xc8)
[ 5.133568] [<c0381160>] (i2c_register_driver+0x2c/0xc8) from [<c04ab888>] (do_one_initcall+0x50/0x144)
[ 5.142842] [<c04ab888>] (do_one_initcall+0x50/0x144) from [<c04aba64>] (kernel_init_freeable+0xe8/0x1ac)
[ 5.152293] [<c04aba64>] (kernel_init_freeable+0xe8/0x1ac) from [<c041d214>] (kernel_init+0x8/0xe4)
[ 5.161233] [<c041d214>] (kernel_init+0x8/0xe4) from [<c020e298>] (ret_from_fork+0x14/0x3c)
[ 5.169471] Code: 03c7703f 1a000025 e59f0214 eb039ba7 (e59a3044)
[ 5.175507] ---[ end trace 3e6eedf8393bc047 ]---
[ 5.180035] note: swapper[1] exited with preempt_count 1
[ 5.185368] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 5.185368]
This is happening with a (likely broken) gpio driver, but it would be
better to get an error message rather than a panic in that case, I think.
I wrote the following patch as a workaround, but I'm not sure if this
is the best solution. It's a bit kludgy. It fixes the code in
gpiod_request, but the same problem is present in other routines
(gpiod_direction_input, gpiod_direction_output, gpiod_set_debounce).
Since this is something of a corner case, I'm not sure if the null check
should be added to desc_to_gpio(), but that's another way to handle it.
Technically, code should not be calling those other routines without
having done a gpio_request() first, so maybe this is sufficient.
Let me know what you think.
Thanks,
-- Tim Bird
Senior Software Engineer, Sony Mobile Communication
Architecture Group Chair, CE Workgroup, Linux Foundation
Here's my patch:
Subject: [PATCH] gpio: avoid panic on NULL desc->chip in gpiod_request
Avoid calling desc_to_gpio if desc->chip is NULL, as this will
cause a kernel panic.
In the code above this, there is a test for chip==NULL, which
comes to the 'done' label if true. In this case, the code
panics, since desc_to_gpio() uses desc->chip to look up the
gpio number.
The possibility of calling desc_to_gpio() with a NULL desc->chip
is present in other locations (gpiod_direction_input,
gpiod_direction_output, gpiod_set_debounce) which this fix
doesn't catch.
Signed-off-by: Tim Bird <tim.bird@...ymobile.com>
---
drivers/gpio/gpiolib.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index ff0fd65..61e9963 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1445,9 +1445,15 @@ static int gpiod_request(struct gpio_desc *desc, const char *label)
spin_lock_irqsave(&gpio_lock, flags);
}
done:
- if (status)
- pr_debug("_gpio_request: gpio-%d (%s) status %d\n",
- desc_to_gpio(desc), label ? : "?", status);
+ if (status) {
+ if (desc->chip) {
+ pr_debug("_gpio_request: gpio-%d (%s) status %d\n",
+ desc_to_gpio(desc), label ? : "?", status);
+ } else {
+ pr_debug("_gpio_request: gpio-?? (%s) status %d\n",
+ label ? : "?", status);
+ }
+ }
spin_unlock_irqrestore(&gpio_lock, flags);
return status;
}
-- 1.8.2.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists