From: "Kaigai Kohei" <kaigai@ak.jp.nec.com>
To: linux-ia64@vger.kernel.org, selinux@tycho.nsa.gov
Cc: James Morris <jmorris@redhat.com>
Subject: Re: [PATCH] Kernel panic on IA-64 Linux with SELinux
Date: Fri, 11 Jun 2004 01:13:38 +0000 [thread overview]
Message-ID: <004d01c44f51$543a2ae0$f97d220a@linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: Xine.LNX.4.44.0406101657420.8385-100000@thoron.boston.redhat.com
James Morris wrote:
> Were you using a standard kernel, or was this a vendor or otherwise
> patched kernel? I know people have booted IA64 with SELinux enabled in
> recent times with no problems.
Yes, I booted up both of the standard kernel (2.6.6) with both of the previous patches.
SELinux was configured to the Permissive-mode.
(I have not tried to boot up with the Enforcing-mode.)
I'm interested in the case you mentioned.
In my experience, kernel panic always occurs while booting up.
What is written in /etc/sysconfig/selinux?
--------
Kaigai Kohei, Linux Promotion Center, NEC
E-mail: kaigai@ak.jp.nec.com
next parent reply other threads:[~2004-06-11 1:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Xine.LNX.4.44.0406101657420.8385-100000@thoron.boston.redhat.com>
2004-06-11 1:13 ` Kaigai Kohei [this message]
2004-06-09 4:36 [PATCH] Kernel panic on IA-64 Linux with SELinux
2004-06-09 14:40 ` Kazuto MIYOSHI
2004-06-09 21:55 ` David Mosberger
2004-06-09 22:44 ` Luck, Tony
2004-06-09 23:25 ` David Mosberger
2004-06-09 23:35 ` Luck, Tony
2004-06-10 0:58 ` David Mosberger
2004-06-10 5:19 ` Luck, Tony
2004-06-10 5:23 ` David Mosberger
2004-06-10 5:28 ` Luck, Tony
2004-06-15 2:28 ` Kaigai Kohei
2004-06-15 4:17 ` Luck, Tony
2004-06-15 4:23 ` David Mosberger
2004-06-15 4:25 ` Luck, Tony
2004-06-15 4:25 ` David Mosberger
2004-06-15 9:37 ` Kaigai Kohei
2004-06-15 12:52 ` Kaigai Kohei
2004-06-17 1:10 ` David Mosberger
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='004d01c44f51$543a2ae0$f97d220a@linux.bs1.fc.nec.co.jp' \
--to=kaigai@ak.jp.nec.com \
--cc=jmorris@redhat.com \
--cc=linux-ia64@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox