linux-kernel - Re: [PATCH resend] kernel/async.c: fixing compilation warnings

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:	Sat, 15 Jan 2011 11:11:38 +0000
From:	Jack Stone <jwjstone@...tmail.fm>
To:	Arjan van de Ven <arjan@...ux.intel.com>
CC:	Viresh Kumar <viresh.kumar@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH resend] kernel/async.c: fixing compilation warnings

"Arjan van de Ven" <arjan@...ux.intel.com> wrote:

>On 1/14/2011 10:39 AM, Jack Stone wrote:
>> On 14/01/2011 15:27, Arjan van de Ven wrote:
>>> On 1/14/2011 5:13 AM, Jack Stone wrote:
>>>> rning: ‘calltime.tv64’ may be used uninitialized in this function
>>> which is clearly a.. gcc funny to be honest. it's a false positive
>by
>>> any stretch.
>>>
>> Agreed. Who should merge this?
>
>should it be?
>traditionally we have shied away for workarounds for false positives 
>from gcc.....

I don't mind. I thought that was what uninitalized_var() was for.

Thanks,

Jack


-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
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/