From: Vasiliy Kulikov <segoon@openwall.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, James Morris <jmorris@namei.org>,
x86@kernel.org, kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [kernel-hardening] Re: [RFC] x86: restrict pid namespaces to 32 or 64 bit syscalls
Date: Sat, 13 Aug 2011 20:32:52 +0400 [thread overview]
Message-ID: <20110813163252.GA18458@albatros> (raw)
In-Reply-To: <36fcaf94-2e99-47cb-a835-aefb79856429@email.android.com>
On Sat, Aug 13, 2011 at 10:41 -0500, H. Peter Anvin wrote:
> IA64 is totally different.
I didn't say all IA-32 compatibility layer of x86 is a crap, surely no.
But there is some code, which is poorly tested exactly because it is
compatibility code. One relatively recent example:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3e645d6b485446c54c6745c5e2cf5c528fe4deec
> I'm extremely sceptical to this patch;
> it feels like putting code in a super-hot path to paper over a problem that has to be fixed anyway.
I'll move the check to the tracesys branch, which is not a hot path, in
the next RFC version, so this should not be a problem.
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
next prev parent reply other threads:[~2011-08-13 16:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 15:03 [RFC] x86: restrict pid namespaces to 32 or 64 bit syscalls Vasiliy Kulikov
2011-08-12 20:08 ` H. Peter Anvin
2011-08-13 6:22 ` Vasiliy Kulikov
2011-08-13 15:41 ` H. Peter Anvin
2011-08-13 16:32 ` Vasiliy Kulikov [this message]
2011-08-14 9:09 ` Solar Designer
2011-08-18 14:40 ` [RFC v2] " Vasiliy Kulikov
2011-08-14 2:38 ` [RFC] " Andi Kleen
2011-08-14 5:08 ` H. Peter Anvin
2011-08-14 9:20 ` Solar Designer
2011-08-14 14:48 ` H. Peter Anvin
2011-08-14 15:27 ` Andi Kleen
2011-08-14 15:36 ` H. Peter Anvin
2011-08-14 23:29 ` James Morris
2011-08-15 0:18 ` Andi Kleen
2011-08-15 0:32 ` [kernel-hardening] " Will Drewry
2011-08-15 0:58 ` Andi Kleen
2011-08-14 16:08 ` Vasiliy Kulikov
2011-08-15 18:51 ` Solar Designer
2011-08-15 18:59 ` H. Peter Anvin
2011-08-15 20:14 ` Solar Designer
2011-08-15 20:27 ` Andi Kleen
2011-08-15 20:48 ` H. Peter Anvin
2011-08-15 22:13 ` Eric Paris
2011-08-16 1:18 ` Andi Kleen
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=20110813163252.GA18458@albatros \
--to=segoon@openwall.com \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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