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]

Message-ID: <20060803201402.GA6828@martell.zuzino.mipt.ru>
Date:	Fri, 4 Aug 2006 00:14:02 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Dave Jones <davej@...hat.com>, Adrian Bunk <bunk@...sta.de>,
	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 03:44:10PM -0400, Dave Jones wrote:
> 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.

Feature bits are only (indirectly) visible via /proc/cpuinfo.
struct cpuinfo_x86, AFAICS, is never copied to userspace. So, it's safe
to remove this header.

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