From: Steve G <linux_4ever@yahoo.com>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Stephen Smalley <sds@epoch.ncsc.mil>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: Ext3 problems in dual booting machine with SE Linux
Date: Fri, 23 Jul 2004 12:01:04 -0700 (PDT) [thread overview]
Message-ID: <20040723190104.48863.qmail@web50609.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407231333000.4446@devserv.devel.redhat.com>
>You may have hit either the 2.4/2.6 xattr compatibility bug, or some other
>xattr bug since fixed in the kernel. I'd suggest using a 2.4.25 or
>greater kernel if you want to access ext2/ext3 xattrs which were created
>under 2.6. 2.4 kernels below this do not have 2.6 compatible xattrs for
>ext2 and ext3.
If Ext3 is now no longer compatible with itself, should it have been called Ext4?
Is there any version number embedded in the filesystem so newer versions of Ext3
can act in a way compatible with older systems?
This seems like an open door to mischief. Any removable media can now be used to
oops a kernel. There are systems that are under configuration control and moving
to 2.4.25 is not really an option. They should be able to read/write any ext3
media inserted into them.
Also look at the 2nd question in section 1.3 of the Fedora Core 2 SE Linux FAQ
page. It does not say using SE Linux will massively corrupt your system when you
reboot into non-selinux systems.
-Steve Grubb
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-07-23 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 15:37 Steve G
2004-07-23 17:37 ` James Morris
2004-07-23 19:01 ` Steve G [this message]
2004-07-23 19:44 ` Stephen C. Tweedie
2004-07-23 20:58 ` Valdis.Kletnieks
2004-07-23 20:46 ` Valdis.Kletnieks
2004-07-23 21:21 ` Steve G
2004-07-23 21:28 ` Valdis.Kletnieks
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=20040723190104.48863.qmail@web50609.mail.yahoo.com \
--to=linux_4ever@yahoo.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=sds@epoch.ncsc.mil \
/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
all inboxes | Powered by JetHome®