netdev - Re: authenc compile warnings in current net-2.6.24

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 Oct 2007 18:38:35 +0200
From:	Oliver Hartkopp <socketcan@...tkopp.net>
To:	Sebastian Siewior <netdev@...breakpoint.cc>, netdev@...r.kernel.org
Subject: Re: authenc compile warnings in current net-2.6.24

Sebastian Siewior wrote:
> * David Miller | 2007-10-10 16:25:28 [-0700]:
>
>   
>> From: Sebastian Siewior <netdev@...breakpoint.cc>
>> Date: Wed, 10 Oct 2007 21:53:37 +0200
>>
>>     
>>> * Oliver Hartkopp | 2007-10-10 19:53:53 [+0200]:
>>>
>>>       
>>>> CC [M] crypto/authenc.o
>>>> crypto/authenc.c: In function ?crypto_authenc_hash?:
>>>> crypto/authenc.c:88: warning: ?cryptlen? may be used uninitialized in this 
>>>> function
>>>> crypto/authenc.c:87: warning: ?dst? may be used uninitialized in this 
>>>> function
>>>> crypto/authenc.c: In function ?crypto_authenc_decrypt?:
>>>> crypto/authenc.c:163: warning: ?cryptlen? may be used uninitialized in this 
>>>> function
>>>> crypto/authenc.c:163: note: ?cryptlen? was declared here
>>>> crypto/authenc.c:162: warning: ?src? may be used uninitialized in this 
>>>> function
>>>> crypto/authenc.c:162: note: ?src? was declared here
>>>>
>>>> do you already know these warnings?
>>>>         
>>> Those warnings are looking like a compiler bug to me.
>>>       
>> To be honest I don't know of any compiler which commits enough
>> flow variable analysis to support doing %100 accurate warnings
>> in situations like this.
>>     
>
> gcc (GCC) 4.1.2 (Gentoo 4.1.2) did not produce any warnings in this
> case.
>
>   

Hi Sebasian,

my gcc was the lastest Debian unstable one:

gcc -v

Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v 
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr 
--enable-shared --with-system-zlib --libexecdir=/usr/lib 
--without-included-gettext --enable-threads=posix --enable-nls 
--with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr 
--enable-targets=all --disable-werror --enable-checking=release 
--build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.2.1 (Debian 4.2.1-5)

Regards,
Oliver


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html