linux-kernel - Re: Userspace visible of 3 include/asm/ headers

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:	Thu, 3 Aug 2006 15:44:10 -0400
From:	Dave Jones <davej@...hat.com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	linux-kernel@...r.kernel.org,
	David Woodhouse <dwmw2@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: Userspace visible of 3 include/asm/ headers

On Thu, Aug 03, 2006 at 09:39:52PM +0200, Adrian Bunk wrote:
 > Could anyone help me regarding the desired userspace visibility of the 
 > following three headers under include/asm/?
 > 
 > 
 > Header        : cpufeature.h
 > Architectures : i386, x86_64
 > Is there any reason why this header is exported to userspace?

Probably not. The only apps I've seen that care about feature bits
define them theirselves rather than use these.

 > Header        : setup.h
 > Architectures : i386, ia64, x86_64
 > Contents:
 > - COMMAND_LINE_SIZE on ia64, x86_64
 > - much more on i386
 > Should COMMAND_LINE_SIZE be visible to userspace?

Bootloaders probably need to know this.

 > Header        : timex.h
 > Architectures : all architectures
 > Offers CLOCK_TICK_RATE on all architectures, but on some architectures
 > (like i386) this depends on the kernel configuration.
 > -> not a userspace header?

Also longer term,  CLOCK_TICK_RATE will make no sense should we go
to a tickless kernel.

		Dave

-- 
http://www.codemonkey.org.uk
-
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/