From: David Miller <davem@davemloft.net>
To: hpa@zytor.com
Cc: a.gruenbacher@computer.org, nathans@sgi.com, bunk@stusta.de,
linux-kernel@vger.kernel.org, jmorris@redhat.com,
dwmw2@infradead.org
Subject: Re: include/linux/xattr.h: how much userpace visible?
Date: Mon, 26 Feb 2007 15:43:08 -0800 (PST) [thread overview]
Message-ID: <20070226.154308.112620497.davem@davemloft.net> (raw)
In-Reply-To: <45E36D39.2030605@zytor.com>
From: "H. Peter Anvin" <hpa@zytor.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
next prev parent reply other threads:[~2007-02-26 23:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 18:43 include/linux/xattr.h: how much userpace visible? Adrian Bunk
2006-07-23 19:26 ` Alexey Dobriyan
2006-07-23 22:57 ` Nathan Scott
2006-07-24 18:31 ` Andreas Gruenbacher
2006-07-24 18:45 ` Sam Ravnborg
2006-07-24 18:58 ` Andreas Gruenbacher
2007-02-26 23:29 ` H. Peter Anvin
2007-02-26 23:28 ` H. Peter Anvin
2007-02-26 23:43 ` David Miller [this message]
2007-02-26 23:52 ` H. Peter Anvin
2007-02-27 0:03 ` Christoph Hellwig
2007-02-27 0:10 ` H. Peter Anvin
2007-02-27 1:49 ` Kyle Moffett
2007-02-27 2:09 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070226.154308.112620497.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.gruenbacher@computer.org \
--cc=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox