linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Eric Paris <eparis@parisplace.org>
Cc: "Steve Grubb" <sgrubb@redhat.com>,
	"Ozan Çağlayan" <ozan@pardus.org.tr>,
	"James Morris" <jmorris@namei.org>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	"Casey Schaufler" <casey@schaufler-ca.com>,
	"David Safford" <safford@watson.ibm.com>,
	"Dave Hansen" <dave@linux.vnet.ibm.com>,
	"Mimi Zohar" <zohar@us.ibm.com>
Subject: Re: [PATCH] security: move LSM xattrnames to xattr.h
Date: Wed, 03 Nov 2010 16:45:12 -0400	[thread overview]
Message-ID: <1288817112.2939.89.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTi=4Tu=26ytCYvZSADtCdAbzw6U_9pxvHRfjwa7K@mail.gmail.com>

On Wed, 2010-11-03 at 16:26 -0400, Eric Paris wrote:
> On Tue, Oct 12, 2010 at 9:40 AM, Mimi Zohar <zohar@linux.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

Thanks Eric. Don't know what happened, but /usr/include/xattr/xattr.h is
gone. /usr/include/sys/xattr.h contains the names of the user space
xattr tools, not the kernel version. I'll create the patch for stable.

thanks,

Mimi





      reply	other threads:[~2010-11-03 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 19:07 [PATCH] security: move LSM xattrnames to xattr.h Mimi Zohar
2010-07-02  0:16 ` James Morris
2010-10-12 11:14   ` Ozan Çağlayan
2010-10-12 13:06     ` Mimi Zohar
2010-10-12 13:19       ` Steve Grubb
2010-10-12 13:40         ` Mimi Zohar
2010-11-03 17:00           ` Steve Grubb
2010-11-03 17:38             ` Mimi Zohar
2010-11-03 17:57               ` Steve Grubb
2010-11-03 19:02                 ` Eric Paris
2010-11-03 19:46                   ` Steve Grubb
2010-11-03 20:26           ` Eric Paris
2010-11-03 20:45             ` Mimi Zohar [this message]

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=1288817112.2939.89.camel@localhost.localdomain \
    --to=zohar@linux.vnet.ibm.com \
    --cc=casey@schaufler-ca.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=ozan@pardus.org.tr \
    --cc=safford@watson.ibm.com \
    --cc=sgrubb@redhat.com \
    --cc=zohar@us.ibm.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;
as well as URLs for NNTP newsgroup(s).