[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=4Tu=26ytCYvZSADtCdAbzw6U_9pxvHRfjwa7K@mail.gmail.com>
Date: Wed, 3 Nov 2010 16:26:34 -0400
From: Eric Paris <eparis@...isplace.org>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc: Steve Grubb <sgrubb@...hat.com>,
Ozan Çağlayan <ozan@...dus.org.tr>,
James Morris <jmorris@...ei.org>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
Casey Schaufler <casey@...aufler-ca.com>,
David Safford <safford@...son.ibm.com>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Mimi Zohar <zohar@...ibm.com>
Subject: Re: [PATCH] security: move LSM xattrnames to xattr.h
On Tue, Oct 12, 2010 at 9:40 AM, Mimi Zohar <zohar@...ux.vnet.ibm.com> wrote:
> On Tue, 2010-10-12 at 09:19 -0400, Steve Grubb wrote:
> Before making any changes to the kernel xattr.h, I want to understand
> the reason for two xattr.h files, one in /usr/include/linux/ and the
> other in /usr/include/xattr/. /usr/include/linux/xattr.h contains those
> elements not defined as __kernel__, while /usr/include/xattr/xattr.h
> contains that and other definitions. Will changing the kernel xattr.h
> version change both?
I don't know what /usr/include/xattr/ is but /usr/include/linux/ is
where the kernel-headers are supposed to end up. I'm guessing
/usr/include/xattr/ is the glibc function definitions? (my glibc
function definitions for xattrs are in /usr/include/sys/xattr.h)
I sent a patch to export them all. I didn't cc stable since it
clearly change more than it needs to, but we really should send
something to stable....
-Eric
--
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/
Powered by blists - more mailing lists