[lkml]   [2014]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] gpiolib: check if gpio_desc pointer is error or NULL
On Wed, Mar 19, 2014 at 5:33 PM, Ben Dooks <> wrote:
> On 19/03/14 02:48, Alexandre Courbot wrote:
>> On Tue, Mar 18, 2014 at 7:41 PM, Ben Dooks <>
>> wrote:
>>> Some of the gpiod_ calls take a pointer to a gpio_desc as their
>>> argument but only check to see if it is NULL to validate the
>>> input.
>>> Calls such as devm_gpiod_get() return an error-pointer if they
>>> fail, so doing the following will not work:
>>> gpio = devm_gpiod_get(...);
>>> gpiod_direction_output(gpio, 0);
>>> The sequence produces an OOPS like:
>>> Unable to handle kernel paging request at virtual address
>>> fffffffe
>>> Change all calls that check for !desc to use IS_ERR_OR_NULL() to
>>> avoid these issues.
>> This change is certainly correct from a semantics point of view. Maybe
>> I'd argue that the burden is on the caller to check that gpiod_get()
>> returns a valid GPIO descriptor, but having extra security doesn't
>> hurt. However my problem with this change in its current form is that
>> it will hide such forgetfulnesses by making functions like
>> gpiod_get_value() fail silently instead of triggering a oops.
> On the other hand, it means that we do not have to keep checking
> the validity of the pointer in the caller.

A very scary perspective which I don't think we should support.
Especially since the pointer only needs to be checked once, after
gpiod_get() is called.

 \ /
  Last update: 2014-03-19 10:21    [W:0.034 / U:19.724 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site