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

Message-ID: <20090112212855.GB15185@uranus.ravnborg.org>
Date:	Mon, 12 Jan 2009 22:28:55 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Can we get warnings from the x86 userspace headers fixed?

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

	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/