linux-kernel - Re: include/linux/xattr.h: how much userpace visible?

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:	Mon, 26 Feb 2007 16:10:16 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Christoph Hellwig <hch@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	David Miller <davem@...emloft.net>, a.gruenbacher@...puter.org,
	bunk@...sta.de, linux-kernel@...r.kernel.org, jmorris@...hat.com,
	dwmw2@...radead.org
Subject: Re: include/linux/xattr.h: how much userpace visible?

Christoph Hellwig wrote:
> What's the problem of exposing all these APIs unconditionally?
> glibcs should either use all information from the linux/ headers
> or nothing at all, but not depend on hiding some bits.

It's not always that simple.  In particular, in some files there might 
be typedefs or structure tags that step on libc's namespace (but are 
useful to other libcs), but ABI constants that are universally useful.

One way to deal with the particular issue of structure tags which is 
probably even more useful is:

#if defined(__KERNEL__) || defined(__KERNEL_EXPORT_STRUCTURES)
# define __kstruct_stat stat
#endif

struct __kstruct_stat {
	/* ...foo... */
};

... which lets the libc export it into whatever namespace it wants by 
#defining __kstruct macros accordingly.

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