All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Eric Paris <eparis@parisplace.org>
Cc: Solar Designer <solar@openwall.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andi Kleen <andi@firstfloor.org>,
	Vasiliy Kulikov <segoon@openwall.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, James Morris <jmorris@namei.org>,
	kernel-hardening@lists.openwall.com, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Will Drewry <wad@chromium.org>
Subject: [kernel-hardening] Re: [RFC] x86: restrict pid namespaces to 32 or 64 bit syscalls
Date: Tue, 16 Aug 2011 03:18:07 +0200	[thread overview]
Message-ID: <20110816011807.GA5782@one.firstfloor.org> (raw)
In-Reply-To: <CACLa4puLxL+azpYjQsD6eDKU=LPJ1mrF1LUrc5Gy-89a8fvjpQ@mail.gmail.com>

On Mon, Aug 15, 2011 at 06:13:51PM -0400, Eric Paris wrote:
> On Mon, Aug 15, 2011 at 4:14 PM, Solar Designer <solar@openwall.com> wrote:
> 
> > So how do we proceed from here?  Start by getting Will's patch applied?
> 
> How to move forward with Will's patch is supposed to be discussed at
> the invite only kernel summit October 23 - 25, 2011.  As one of the

linux-kernel is really the primary forum. If you want to discuss
something just discuss it here (ideally with patches)

May the best patch win.

-Andi

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Eric Paris <eparis@parisplace.org>
Cc: Solar Designer <solar@openwall.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andi Kleen <andi@firstfloor.org>,
	Vasiliy Kulikov <segoon@openwall.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, James Morris <jmorris@namei.org>,
	kernel-hardening@lists.openwall.com, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Will Drewry <wad@chromium.org>
Subject: Re: [RFC] x86: restrict pid namespaces to 32 or 64 bit syscalls
Date: Tue, 16 Aug 2011 03:18:07 +0200	[thread overview]
Message-ID: <20110816011807.GA5782@one.firstfloor.org> (raw)
In-Reply-To: <CACLa4puLxL+azpYjQsD6eDKU=LPJ1mrF1LUrc5Gy-89a8fvjpQ@mail.gmail.com>

On Mon, Aug 15, 2011 at 06:13:51PM -0400, Eric Paris wrote:
> On Mon, Aug 15, 2011 at 4:14 PM, Solar Designer <solar@openwall.com> wrote:
> 
> > So how do we proceed from here?  Start by getting Will's patch applied?
> 
> How to move forward with Will's patch is supposed to be discussed at
> the invite only kernel summit October 23 - 25, 2011.  As one of the

linux-kernel is really the primary forum. If you want to discuss
something just discuss it here (ideally with patches)

May the best patch win.

-Andi

  reply	other threads:[~2011-08-16  1:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 15:03 [kernel-hardening] [RFC] x86: restrict pid namespaces to 32 or 64 bit syscalls Vasiliy Kulikov
2011-08-12 15:03 ` Vasiliy Kulikov
2011-08-12 20:08 ` [kernel-hardening] " H. Peter Anvin
2011-08-12 20:08   ` H. Peter Anvin
2011-08-13  6:22   ` [kernel-hardening] " Vasiliy Kulikov
2011-08-13  6:22     ` Vasiliy Kulikov
2011-08-13 15:41     ` [kernel-hardening] " H. Peter Anvin
2011-08-13 15:41       ` H. Peter Anvin
2011-08-13 16:32       ` [kernel-hardening] " Vasiliy Kulikov
2011-08-14  9:09         ` Solar Designer
2011-08-14  9:09           ` Solar Designer
2011-08-18 14:40         ` [kernel-hardening] [RFC v2] " Vasiliy Kulikov
2011-08-18 14:40           ` Vasiliy Kulikov
2011-08-14  2:38       ` [kernel-hardening] Re: [RFC] " Andi Kleen
2011-08-14  2:38         ` Andi Kleen
2011-08-14  5:08         ` [kernel-hardening] " H. Peter Anvin
2011-08-14  5:08           ` H. Peter Anvin
2011-08-14  9:20           ` [kernel-hardening] " Solar Designer
2011-08-14  9:20             ` Solar Designer
2011-08-14 14:48             ` [kernel-hardening] " H. Peter Anvin
2011-08-14 14:48               ` H. Peter Anvin
2011-08-14 15:27               ` [kernel-hardening] " Andi Kleen
2011-08-14 15:27                 ` Andi Kleen
2011-08-14 15:36                 ` [kernel-hardening] " H. Peter Anvin
2011-08-14 15:36                   ` H. Peter Anvin
2011-08-14 23:29                   ` [kernel-hardening] " James Morris
2011-08-14 23:29                     ` James Morris
2011-08-15  0:18                   ` [kernel-hardening] " Andi Kleen
2011-08-15  0:18                     ` Andi Kleen
2011-08-15  0:32                     ` [kernel-hardening] " Will Drewry
2011-08-15  0:58                       ` Andi Kleen
     [not found]                 ` <20110814152729.GU5782-qrUzlfsMFqo/4alezvVtWx2eb7JE58TQ@public.gmane.org>
2011-08-14 16:08                   ` Vasiliy Kulikov
2011-08-14 16:08                     ` Vasiliy Kulikov
2011-08-14 16:08                     ` [kernel-hardening] " Vasiliy Kulikov
2011-08-15 18:51               ` Solar Designer
2011-08-15 18:51                 ` Solar Designer
2011-08-15 18:59                 ` [kernel-hardening] " H. Peter Anvin
2011-08-15 18:59                   ` H. Peter Anvin
2011-08-15 20:14                   ` [kernel-hardening] " Solar Designer
2011-08-15 20:14                     ` Solar Designer
2011-08-15 20:27                     ` [kernel-hardening] " Andi Kleen
2011-08-15 20:27                       ` Andi Kleen
2011-08-15 20:48                     ` [kernel-hardening] " H. Peter Anvin
2011-08-15 20:48                       ` H. Peter Anvin
2011-08-15 22:13                     ` [kernel-hardening] " Eric Paris
2011-08-15 22:13                       ` Eric Paris
2011-08-16  1:18                       ` Andi Kleen [this message]
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=20110816011807.GA5782@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=eparis@parisplace.org \
    --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=segoon@openwall.com \
    --cc=solar@openwall.com \
    --cc=tglx@linutronix.de \
    --cc=wad@chromium.org \
    --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 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.