From: Thorsten Kukuk <kukuk@suse.de>
To: selinux@tycho.nsa.gov
Subject: Re: Filesystem problems
Date: Wed, 15 Oct 2003 09:29:49 +0200 [thread overview]
Message-ID: <20031015072949.GA12602@suse.de> (raw)
In-Reply-To: <1066191058.3f8cc8d257e4c@eaglemail.unt.edu>
On Tue, Oct 14, Ignacio Tripodi wrote:
> I had a 2.4 kernel with SELinux enabled, could load a policy, relabeled the
> filesystem (ext3) and was able to see the extended attributes of all files.
> However, after I upgraded to the 2.6 SELinux kernel, I wasn't able to load
> the policy again. It still lets me in since I enabled the development mode
> but the tools don't recognize the running kernel as an SELinux-enabled
> kernel. Besides, this is what I get in the dmesg after it mounts the root
> filesystem:
>
> security_context_to_sid: called before initial load_policy on unknown
> context system_u:object_
> r:file_t
> security_context_to_sid: called before initial load_policy on unknown
> context system_u:object_
> r:root_t
With kernel 2.6.0-test7, I have a lot of ext3 problems with SELinux
enabled, which always ends in a filesystem crash and a necessary
fsck.ext3 run at the next boot. Don't know if this comes from the
usage of extended attributes or if ext3 itself is broken in 2.6.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
--
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.
next prev parent reply other threads:[~2003-10-15 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 4:10 Filesystem problems Ignacio Tripodi
2003-10-15 7:29 ` Thorsten Kukuk [this message]
2003-10-15 18:22 ` Stephen Smalley
2003-10-15 18:36 ` Thorsten Kukuk
2003-10-15 18:39 ` Stephen Smalley
2003-10-15 13:13 ` James Morris
2003-10-15 16:29 ` Ignacio Tripodi
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=20031015072949.GA12602@suse.de \
--to=kukuk@suse.de \
--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.