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]

Message-ID: <20060724184534.GA26842@mars.ravnborg.org>
Date:	Mon, 24 Jul 2006 20:45:34 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Andreas Gruenbacher <a.gruenbacher@...puter.org>
Cc:	Nathan Scott <nathans@....com>, Adrian Bunk <bunk@...sta.de>,
	linux-kernel@...r.kernel.org, James Morris <jmorris@...hat.com>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: include/linux/xattr.h: how much userpace visible?

On Mon, Jul 24, 2006 at 08:31:11PM +0200, 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.
The userspace headers are supposed to hold the part of the kernel
definitions that glibc (and mayby the attr package) uses. If they happen
to have their own copy now should not impct the decision what is part of
the userspace interface for the kernel. So actual usage does not decide
what is part of the userspace kernel headers but what definitionas are
definitions the userspace <-> kernel interface.

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