linux-kernel - Re: [RFC][PATCH] futex: Hide false positive about uninit var usage

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:	Tue, 16 Nov 2010 09:30:39 -0800
From:	Darren Hart <dvhart@...ux.intel.com>
To:	"Aguirre, Sergio" <saaguirre@...com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>, Namhyung Kim <namhyung@...il.com>
Subject: Re: [RFC][PATCH] futex: Hide false positive about uninit var usage

On 11/16/2010 08:59 AM, Aguirre, Sergio wrote:
> Hi Darren,
>
>> -----Original Message-----
>> From: Darren Hart [mailto:dvhart@...ux.intel.com]
>> Sent: Tuesday, November 16, 2010 10:43 AM
>> To: Aguirre, Sergio
>> Cc: LKML; Thomas Gleixner; Peter Zijlstra; Ingo Molnar; Namhyung Kim
>> Subject: Re: [RFC][PATCH] futex: Hide false positive about uninit var
>> usage
>>
>> On 11/16/2010 08:32 AM, Sergio Aguirre wrote:
>>> In exit_robust_list, there was this warning shown:
>>>
>>> kernel/futex.c: In function 'exit_robust_list':
>>> kernel/futex.c:2492: warning: 'next_pi' may be used uninitialized in
>> this function
>>>
>>> Which is a false positive, since in the function, the only scenario
>>> possible in which the var is read, is after a successful excecution of
>>> fetch_robust_entry, which populates the variable.
>>>
>>> So there's no real possibility of it being used uninitialized.
>>
>> Hi Sergio,
>>
>> You are correct. Thomas has recently pulled my fix for this into tip, it
>> should be queued for mainline already.
>
> Oh ok. Sorry, I didn't know that. Please ignore this patch then.

No problem. In the future, if you run into problems with futexes, check 
the linux-2.6-tip repository for fixes as that is where they are queued 
up before going into mainline.

git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
branch: core/futexes

Thanks,

Darren

>
> Regards,
> Sergio
>
>>
>> Thanks,
>>
>> Darren Hart
>>
>>>
>>> Signed-off-by: Sergio Aguirre<saaguirre@...com>
>>> Cc: Thomas Gleixner<tglx@...utronix.de>
>>> Cc: Peter Zijlstra<a.p.zijlstra@...llo.nl>
>>> Cc: Darren Hart<dvhart@...ux.intel.com>
>>> Cc: Ingo Molnar<mingo@...e.hu>
>>> Cc: Namhyung Kim<namhyung@...il.com>
>>> ---
>>>    kernel/futex.c |    3 ++-
>>>    1 files changed, 2 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/kernel/futex.c b/kernel/futex.c
>>> index 6c683b3..3646157 100644
>>> --- a/kernel/futex.c
>>> +++ b/kernel/futex.c
>>> @@ -2489,7 +2489,8 @@ void exit_robust_list(struct task_struct *curr)
>>>    {
>>>    	struct robust_list_head __user *head = curr->robust_list;
>>>    	struct robust_list __user *entry, *next_entry, *pending;
>>> -	unsigned int limit = ROBUST_LIST_LIMIT, pi, next_pi, pip;
>>> +	unsigned int limit = ROBUST_LIST_LIMIT, pi;
>>> +	unsigned int uninitialized_var(next_pi), pip;
>>>    	unsigned long futex_offset;
>>>    	int rc;
>>>
>>
>>
>> --
>> Darren Hart
>> Yocto Linux Kernel


-- 
Darren Hart
Yocto Linux Kernel
--
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/