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]
Date:	Tue, 13 Jan 2009 01:14:12 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Can we get warnings from the x86 userspace headers fixed?

[Sam Ravnborg - Mon, Jan 12, 2009 at 10:28:55PM +0100]
| 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
| 

Sam, I hope to find some spare time for this
tomorrow (it's night here). At least in one
moment headers_check assume that CONFIG is exported
into user space even being bound by pure C comments.

---
/home/cyrill/projects/kernel/linux-2.6.git/usr/include/asm/e820.h:13: leaks
CONFIG_NODES to userspace where it is not valid
---

Just a note.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ