linux-kernel - Re: [PATCH] staging: binder: cmd

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]

Message-ID: <CAAX90H1ToZWJ5WNOtUL+c4no9iuSrzyE+WHJ1SEgyfaajiT2ag@mail.gmail.com>
Date:	Mon, 8 Sep 2014 16:42:56 +0400
From:	Dmitry Voytik <voytikd@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: binder: cmd_name must be initialised

On Fri, Sep 5, 2014 at 10:48 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Fri, Sep 05, 2014 at 08:02:24PM +0400, Dmitry Voytik wrote:
>> Variable cmd_name must be initialised as variable name is.
>
> Why?  What bug does this fix?  Have you tested this change?  Does this
> cause binder to now act differently than before?

Hi Greg,

Thank you for your time.
The intent was to eliminate the GCC warning:
 /scratch/kisskb/src/drivers/staging/android/binder.c: warning:
'cmd_name' may be used uninitialized in this function
[-Wuninitialized]:  => 2275:5
But now after carefull review of the sorce code I've understood that
this is a false positive.
Sorry for bothering.

> thanks,
>
> greg k-h



-- 
Best Regards,
Dmitry Voytik.
voytikd@...il.com
--
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/