Message-ID: <45E372CA.9020709@zytor.com>
Date: Mon, 26 Feb 2007 15:52:42 -0800
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: David Miller <davem@davemloft.net>
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?
References: <20060724085701.B2083275@wobbly.melbourne.sgi.com>	<200607242031.11815.a.gruenbacher@computer.org>	<45E36D39.2030605@zytor.com> <20070226.154308.112620497.davem@davemloft.net>
In-Reply-To: <20070226.154308.112620497.davem@davemloft.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 980
Lines: 26

David Miller wrote:
>>>
>> 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

Indeed it is (as well as <linux/stat.h>).

I believe the use of feature macros is probably the way to go; that way 
userspace can request subsets, which can vary from libc to libc.

There is, of course, the "ABI language" variant, but I don't see that 
happening unless someone has a lot of time to spend on it.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/