From: David Safford <safford@watson.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Kylene Jo Hall <kjhall@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
LSM ML <linux-security-module@vger.kernel.org>,
Dave Safford <safford@us.ibm.com>, Mimi Zohar <zohar@us.ibm.com>,
Serge Hallyn <sergeh@us.ibm.com>
Subject: Re: [RFC][PATCH 3/6] SLIM main patch
Date: Fri, 14 Jul 2006 16:51:13 -0400 [thread overview]
Message-ID: <1152910274.2415.10.camel@localhost.localdomain> (raw)
In-Reply-To: <1152905691.314.62.camel@localhost.localdomain>
On Fri, 2006-07-14 at 12:34 -0700, Dave Hansen wrote:
> On Fri, 2006-07-14 at 12:25 -0700, Kylene Jo Hall wrote:
> > > inode_supports_xaddr()? Seems like something that should check a
> > > superblock flag or something.
> >
> > I don't know of any such flags.
>
> There probably aren't any. The superblock may not even be the right
> place for it. It just seems a bit silly to say that the only files in
> the system that don't support xaddrs are device files and /proc. What
> about all of the other filesystems? Have you tested things like
> ISO9660, VFAT, sysfs?
is_exempt() is just a quick test to speed up a couple of obvious cases.
It does not need to be complete, as the subsequent get_level() will handle
all other cases where xattrs are not supported....
dave
next prev parent reply other threads:[~2006-07-14 20:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 17:24 [RFC][PATCH 3/6] SLIM main patch Kylene Jo Hall
2006-07-14 17:44 ` Dave Hansen
2006-07-14 18:06 ` Kylene Jo Hall
2006-07-14 18:28 ` Dave Hansen
2006-07-14 18:27 ` Dave Hansen
2006-07-14 19:25 ` Kylene Jo Hall
2006-07-14 19:34 ` Dave Hansen
2006-07-14 20:51 ` David Safford [this message]
2006-07-14 19:52 ` Serge E. Hallyn
2006-07-14 20:01 ` Kylene Jo Hall
2006-07-14 20:06 ` Dave Hansen
2006-07-15 16:54 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-07-24 17:51 Kylene Jo Hall
2006-07-28 6:01 ` Pavel Machek
2006-07-28 19:05 ` Kylene Jo Hall
2006-07-24 17:51 Kylene Jo Hall
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=1152910274.2415.10.camel@localhost.localdomain \
--to=safford@watson.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@us.ibm.com \
--cc=sergeh@us.ibm.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