linux-kernel - Re: Confusion in usr/include/asm-generic/fcntl.h

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: <4977C1D3.2010801@zytor.com>
Date:	Wed, 21 Jan 2009 16:46:11 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	John David Anglin <dave@...uly1.hia.nrc.ca>
CC:	Grant Grundler <grundler@...isc-linux.org>, arnd@...db.de,
	davem@...emloft.net, jaswinder@...nel.org, mingo@...e.hu,
	x86@...nel.org, linux-kernel@...r.kernel.org,
	linux-parisc@...r.kernel.org
Subject: Re: Confusion in usr/include/asm-generic/fcntl.h

John David Anglin wrote:
>>> CONFIG_64BIT on parisc user space looks very wrong.
>> This shouldn't be exported to user space. Is that what you meant?
> 
> This does get exported to user space as applications sometimes need
> to know whether they are running under a 32 or 64-bit kernel.  See
> config.guess.  However, it certainly would be wrong to use this
> to make decisions about user space.
> 

CONFIG_* macros are not (or at least should not) be exported to 
userspace!  Userspace should not make compile-time decisions based on 
kernel configuration -- a runtime property!

	-hpa

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