From: Michael Tiemann <tiemann@redhat.com>
To: Jose Nazario <jose@biocserver.bioc.cwru.edu>
Cc: Howard Holm <hdholm@epoch.ncsc.mil>,
kmrussel@hsc.vcu.edu, selinux@tycho.nsa.gov
Subject: Re: SELinux compatible with XFS?
Date: Tue, 20 Mar 2001 07:06:13 -0500 [thread overview]
Message-ID: <3AB747B5.7050603@redhat.com> (raw)
In-Reply-To: Pine.LNX.4.30.0103191346050.24251-100000@biocserver.BIOC.CWRU.Edu
We've been doing extensive testing of the 2.4 kernel, and there are all
sorts of exciting ways in which it can corrupt _any_ filesystem (it's one
reason we haven't released a 2.4-based product ;-). We're working hard
with others to fix those problems. I wouldn't blame XFS just yet.
M
Jose Nazario wrote:
> On Mon, 19 Mar 2001, Howard Holm wrote:
>
>
>> While I'm not completely familiar with XFS, my understanding is that
>> one of its advantages is that it stores extended attributes with the
>> files. So, it should, hopefully, be relatively easy to add a PSID to
>> the extended file attributes. That said, it isn't one of NSA's
>> priorities to add that support. If someone else wants it enough to do
>> the work, we'd certainly like to see the results made available.
>
>
> i'd like to chime in with some notes from the field and some links.
>
> first up, we've just migrated *away* from XFS on some early 2.4 kernels on
> out local LUG server, lockups and IO problems were just too great. that is
> to say that this may have been fixed in recent releases of the 2.4 kernel
> and the XFS source. i hope so, we would hover around 8 hours of uptime on
> a busy server.
>
> however, Linus is not happy to import large chunks of code into the
> kernel, which will probably slow the adoption of XFS in Linux. also, they
> recently officialy merged Reiser in, albeit you have to request
> experimental code.
>
> but, having been using XFS on IRIX for many, many years, i can say it's
> one high performance filesystem. and yes, it does have extended attributes
> on Linux, like MACLs and such. very nice, indeed. hence, with whatever
> little weight i have here (i don't code stuff for you guys, for example),
> i would like to vote for XFS in SELinux over other filesystems. i know
> that SGI could use the help, and i know that the features of XFS would be
> well utilized in SELinux.
>
> some papers on XFS have appeared, and are available in large measure at:
>
> http://linux-xfs.sgi.com/projects/xfs/publications.html
>
> later,
>
> ____________________________
> jose nazario jose@cwru.edu
> PGP: 89 B0 81 DA 5B FD 7E 00 99 C3 B2 CD 48 A0 07 80
> PGP key ID 0xFD37F4E5 (pgp.mit.edu)
>
>
> --
> You have received this message because you are subscribed to the selinux 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.
--
You have received this message because you are subscribed to the selinux 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.
next prev parent reply other threads:[~2001-03-20 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 16:45 SELinux compatible with XFS? Howard Holm
2001-03-19 18:51 ` Jose Nazario
2001-03-20 12:06 ` Michael Tiemann [this message]
2001-03-20 20:24 ` Florin Andrei
-- strict thread matches above, loose matches on Subject: below --
2001-03-18 20:55 K Mitchell Russell
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=3AB747B5.7050603@redhat.com \
--to=tiemann@redhat.com \
--cc=hdholm@epoch.ncsc.mil \
--cc=jose@biocserver.bioc.cwru.edu \
--cc=kmrussel@hsc.vcu.edu \
--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.