From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S965919AbcCKIxy (ORCPT <rfc822;w@1wt.eu>);
	Fri, 11 Mar 2016 03:53:54 -0500
Received: from mail-wm0-f67.google.com ([74.125.82.67]:34684 "EHLO
	mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S965780AbcCKIxG (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 11 Mar 2016 03:53:06 -0500
Date: Fri, 11 Mar 2016 09:53:01 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>, Ingo Molnar <mingo@redhat.com>,
        Hector Marco-Gisbert <hecmargi@upv.es>,
        LKML <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>,
        "x86@kernel.org" <x86@kernel.org>,
        Ismael Ripoll Ripoll <iripoll@upv.es>,
        Harvey Harrison <harvey.harrison@gmail.com>
Subject: Re: [PATCH] x86: Enable full randomization on i386 and X86_32.
Message-ID: <20160311085301.GB29750@gmail.com>
References: <1457639460-5242-1-git-send-email-hecmargi@upv.es>
 <CAGXu5jJRVrMxgO0G2BjU2Ks=Pa1RcG3LidqXPe9zb-V1LbQv4g@mail.gmail.com>
 <56E1DEE6.5040306@linux.intel.com>
 <CAGXu5j+ZduNvorq5xW5J_NWzN6XQG16Q6_ir5JS1TOfeoFqaMg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGXu5j+ZduNvorq5xW5J_NWzN6XQG16Q6_ir5JS1TOfeoFqaMg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Kees Cook <keescook@chromium.org> wrote:

> On Thu, Mar 10, 2016 at 12:53 PM, Arjan van de Ven
> <arjan@linux.intel.com> wrote:
> >> Arjan, or other folks, can you remember why x86_32 disabled mmap
> >> randomization here? There doesn't seem to be a good reason for it that
> >> I see.
> >
> >
> > for unlimited stack it got really messy with threaded apps.
> 
> Seems like it'd only cause problems for really really giant processes?
> (I think it's telling that the other 32-bit archs don't disable ASLR
> in this case...)

IIRC there was some sort of specific breakage with unlimited stack apps - I don't 
remember the exact details.

> > anyway, I don't mind seeing if this will indeed work, with time running out 
> > where 32 bit is going extinct... in a few years we just won't have enough 
> > testing on this kind of change anymore.
> 
> Sounds good. Ingo, can you pull this in and we can try it for -next?

Ok, we can certainly try. If there's breakage with old distros then we might need 
to put this behind a legacy Kconfig switch.

Thanks,

	Ingo