linux-kernel - Re: Zillions of warnings in -next

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091027222112.74058162@lxorguk.ukuu.org.uk>
Date:	Tue, 27 Oct 2009 22:21:12 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Gregory Haskins" <ghaskins@...ell.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: Zillions of warnings in -next

> I just did a 32-bit build and indeed reproduced the warnings.  However, the warnings
> appear to be dubious as the code is properly (afaict) annotated with explicit casts, and
> I believe they are doing what I intended.
> 
> Basically I have structures that are always 64 bit (so we can have a mixed-mode 32-bit
> guest talk to a 64-bit hypervisor, for instance).  Therefore I am casting between native
> and u64, but the compiler doesn't like this.  Does anyone have any suggestions on ways
> to fix this so the compiler is happy?

	foo = (void *)(unsigned long)x

works for the general case because Linux assumes ptr fits ulong

Similarly in the other direction.

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