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  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]
Date:	Tue, 27 Oct 2009 14:53:33 -0600
From:	"Gregory Haskins" <>
To:	"Alan Cox" <>,
Subject: Re: Zillions of warnings in -next

>>> On 10/27/2009 at 11:25 AM, in message
<>, Alan Cox
<> wrote: 
> I was thinking "what a lot of new warnings". Then I dug a little deeper
> and it seems that someone never bothered to try and build
> drivers/net/vbus-enet.c on a 32bit system.
> So would you mind fixing the 27 new warnings introduced ?
> Alan

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?

For instance:

struct foo {
   u64 bar;

xmit_foo(void *ptr)
 struct foo f;

 f->bar = (u64)ptr; /* generates warning */

Kind Regards,

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists