From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] Kernel panic on IA-64 Linux with SELinux
Date: Wed, 09 Jun 2004 23:25:59 +0000 [thread overview]
Message-ID: <16583.40071.498807.557162@napali.hpl.hp.com> (raw)
In-Reply-To: <013f01c44ddb$636d4aa0$f97d220a@linux.bs1.fc.nec.co.jp>
>>>>> On Wed, 9 Jun 2004 15:44:09 -0700, "Luck, Tony" <tony.luck@intel.com> said:
Tony> I think it would be better to fix up init_task so that it
Tony> appeared to be in region 7 (that way it isn't a special case
Tony> ... it just looks like every other task). BUT, I'm not sure
Tony> how easy that is to do without surgery to generic files
Tony> (places that use "&init_task").
For the particular case of the init_task, we could just fix it up
at boot time (as suggested by the earlier patch).
My bigger worry is that this will be an issue _whenever_ somebody
initializes a linked list with a static initializer. There needs to
be a way to protect from this happening accidentially. Without that,
I'm not sure the virtual remapping is really viable.
--david
next prev parent reply other threads:[~2004-06-09 23:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <Xine.LNX.4.44.0406101657420.8385-100000@thoron.boston.redhat.com>
2004-06-11 1:13 ` Kaigai Kohei
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=16583.40071.498807.557162@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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