linux-kernel - Re: Can we get warnings from the x86 userspace headers fixed?

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: <20090112213655.GA15312@uranus.ravnborg.org>
Date:	Mon, 12 Jan 2009 22:36:55 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Harvey Harrison <harvey.harrison@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Can we get warnings from the x86 userspace headers fixed?

On Mon, Jan 12, 2009 at 01:31:03PM -0800, Harvey Harrison wrote:
> On Mon, 2009-01-12 at 22:28 +0100, Sam Ravnborg wrote:
> > Hi Ingo.
> > 
> > We have recently introduced a lot of new warnings for our
> > userspace headers.
> > 
> > Try to do a "make headers_check" and enjoy...
> > 
> > Are there any chance you could ask one of your helpers to
> > start to look into the x86 specific ones?
> > 
> > If we get x86 clean this would create more incentive to
> > make the generic clean too.
> > 
> > I had originally planned to attack the generic headers
> > (include/linux/*) but I'm faced by reality after my
> > vacation and has almost no spare time for the time being.
> > 
> > I already fixed the sparc headers but that is not 
> > visible compared to x86 (the fixes was btw easy).
> > 
> > I can try to help by doing a few reviews in the
> > beginning but I need to fix kbuild stuff first where
> > I have a few serious issues pending. And lacks time...
> > 
> 
> I'll have a go at some of them this afternoon unless someone beats me to it.

Thanks Harvey!

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