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 15:43:08 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	hpa@...or.com
Cc:	a.gruenbacher@...puter.org, nathans@....com, bunk@...sta.de,
	linux-kernel@...r.kernel.org, jmorris@...hat.com,
	dwmw2@...radead.org
Subject: Re: include/linux/xattr.h: how much userpace visible?

From: "H. Peter Anvin" <hpa@...or.com>
Date: Mon, 26 Feb 2007 15:28:57 -0800

> Andreas Gruenbacher wrote:
> > On Monday, 24 July 2006 00:57, Nathan Scott wrote:
> >> On Sun, Jul 23, 2006 at 08:43:43PM +0200, Adrian Bunk wrote:
> >>> Hi,
> >>>
> >>> how much of include/linux/xattr.h has to be part of the userspace kernel
> >>> headers?
> >> None, I think.
> > 
> > None, indeed. The attr package comes with it own version of xattr.h that also 
> > includes definitions of XATTR_CREATE and XATTR_REPLACE.
> > 
> 
> However, it would be better if the ABI constants were exported, or at 
> least *exportable* (using a __KERNEL_XATTR_MACROS test macro or 
> something like that.)

This is the same situation as the socket.h issue we're trying
to figure out what to do about.

wrt. the socket.h case I think I'm going to revert the guilty
changeset for now until a better scheme is implemented
-
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/