linux-kernel - Re: Warning when compiling arch/x86/mm/init_64.c on x86

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: <484F14B5.4090204@gmail.com>
Date:	Tue, 10 Jun 2008 20:56:37 -0300
From:	Kevin Winchester <kjwinchester@...il.com>
To:	Larry Finger <Larry.Finger@...inger.net>
CC:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Warning when compiling arch/x86/mm/init_64.c on x86_64

Larry Finger wrote:
> Since commit 511631011d39706ac81ee5e4c9084d61e5b4fd34, entitled
> "x86: fix pointer type warning in arch/x86/mm/init_64.c:early_memtest", the 
> following warning is produced for x86_64:
> 
> arch/x86/mm/init_64.c: In function ‘early_memtest’:
> arch/x86/mm/init_64.c:520: warning: passing argument 2 of 
> ‘find_e820_area_size’ from incompatible pointer type
> 
> Before this commit, the compilation of this routine on my system was clean. I 
> use gcc version 4.2.1. Was this the warning for i386 before the patch? I 
> tried simple changes in the definition of find_e820_area_size, but only 
> managed to push the warning on to the call to bad_addr_size. At that point I 
> decided to let the experts find a proper fix. Note that the warning does no 
> harm - I just get nervous about incompatible pointer warnings as it usually 
> means that I have screwed something up.
> 

The patch was against linux-next, which seems to have changed 
find_e820_area_size() - against mainline it introduced the warning 
instead of fixing it.

-- 
Kevin Winchester

--
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/