linux-kernel - Re: [PATCH][next] media: i2c: imx334: Fix a read of the uninitialized variable ret

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 11 Feb 2021 10:50:49 +0000
From:   Colin Ian King <colin.king@...onical.com>
To:     Dan Carpenter <dan.carpenter@...cle.com>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc:     "Paul J . Murphy" <paul.j.murphy@...el.com>,
        Daniele Alessandrelli <daniele.alessandrelli@...el.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Martina Krasteva <martinax.krasteva@...el.com>,
        Gjorgji Rosikopulos <gjorgjix.rosikopulos@...el.com>,
        linux-media@...r.kernel.org, kernel-janitors@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] media: i2c: imx334: Fix a read of the uninitialized
 variable ret

On 11/02/2021 10:41, Dan Carpenter wrote:
> On Wed, Feb 10, 2021 at 11:03:03PM +0200, Sakari Ailus wrote:
>> Hi Colin,
>>
>> On Wed, Feb 10, 2021 at 07:07:52PM +0000, Colin King wrote:
>>> From: Colin Ian King <colin.king@...onical.com>
>>>
>>> Currently there is a dev_err error message that is printing the
>>> error status in variable ret (that has not been set) instead of
>>> the correct error status from imx334->reset_gpio.  Fix this.
>>>
>>> Addresses-Coverity: ("Uninitialized scalar variable")
>>> Fixes: 9746b11715c3 ("media: i2c: Add imx334 camera sensor driver")
>>>
>>> Signed-off-by: Colin Ian King <colin.king@...onical.com>
>>> ---
>>>  drivers/media/i2c/imx334.c | 3 ++-
>>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/media/i2c/imx334.c b/drivers/media/i2c/imx334.c
>>> index 07e31bc2ef18..f8b1caf26c9b 100644
>>> --- a/drivers/media/i2c/imx334.c
>>> +++ b/drivers/media/i2c/imx334.c
>>> @@ -790,7 +790,8 @@ static int imx334_parse_hw_config(struct imx334 *imx334)
>>>  	imx334->reset_gpio = devm_gpiod_get_optional(imx334->dev, "reset",
>>>  						     GPIOD_OUT_LOW);
>>>  	if (IS_ERR(imx334->reset_gpio)) {
>>> -		dev_err(imx334->dev, "failed to get reset gpio %d", ret);
>>> +		dev_err(imx334->dev, "failed to get reset gpio %ld",
>>> +			IS_ERR_VALUE(imx334->reset_gpio));
> 
> IS_ERR_VALUE() isn't right.  It would always print 1 here.  It should
> just be PTR_ERR().
> 
> IS_ERR_VALUE() is like IS_ERR() but for when you're storing memory
> addresses in an unsigned long variable.  get_unmapped_area(), for
> example, returns unsigned longs.
> 
> regards,
> dan carpenter
> 
Thanks, that was a brown paper bug mistake for sure :-/

Colin