From: Eric Paris <eparis@parisplace.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
James Morris <jmorris@namei.org>,
SE Linux <selinux@tycho.nsa.gov>,
rohara@redhat.com
Subject: Re: Latest Ref Policy Diffs
Date: Mon, 12 Dec 2005 13:31:47 -0500 [thread overview]
Message-ID: <1134412307.13662.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1134399286.7305.49.camel@moss-spartans.epoch.ncsc.mil>
> > gfs support is added
>
> I don't think gfs supports security xattrs yet, so I don't think you
> want it to use fs_use_xattr as its labeling mechanism. Even if it did
> support security xattrs, we are going to run into a problem with
> performing the inode security initialization on d_instantiate for remote
> (or userspace) filesystems, because we cannot propagate ERESTARTSYS from
> d_instantiate up the call chain presently, and such filesystems may need
> to return that when they have to wait on a reply from the peer. We'll
> have the same issue for NFSv4.
>
I know Red Hat engineering has added support for security xattrs to GFS
and has it working. I think this is why Dan pushed this upstream. I
don't know if this GFS code is released or anything like that, so I'm
copying the engineer working an it. Hopefully he can also comment on
your other point.
-Eric
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2005-12-12 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 21:14 Latest Ref Policy Diffs Daniel J Walsh
2005-12-09 14:21 ` Christopher J. PeBenito
2005-12-09 14:40 ` Daniel J Walsh
2005-12-09 14:47 ` Christopher J. PeBenito
2005-12-09 21:24 ` Christopher J. PeBenito
2005-12-12 14:54 ` Stephen Smalley
2005-12-12 16:41 ` Christopher J. PeBenito
2005-12-12 18:31 ` Eric Paris [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=1134412307.13662.9.camel@localhost.localdomain \
--to=eparis@parisplace.org \
--cc=dwalsh@redhat.com \
--cc=jmorris@namei.org \
--cc=rohara@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.