Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753851Ab0HWQ0P (ORCPT ); Mon, 23 Aug 2010 12:26:15 -0400 Received: from casper.infradead.org ([85.118.1.10]:51540 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751914Ab0HWQ0N convert rfc822-to-8bit (ORCPT ); Mon, 23 Aug 2010 12:26:13 -0400 Subject: Re: [RFC] mlock/stack guard interaction fixup From: Peter Zijlstra To: ijackson@chiark.greenend.org.uk Cc: Linus Torvalds , Greg KH , Ian Campbell , linux-kernel@vger.kernel.org, stable@kernel.org, stable-review@kernel.org, akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk, Jeremy Fitzhardinge In-Reply-To: <19570.38608.79434.179797@chiark.greenend.org.uk> References: <1282391770.29609.1223.camel@localhost.localdomain> <1282460275.11348.865.camel@localhost.localdomain> <1282462386.11348.871.camel@localhost.localdomain> <1282470917.11348.891.camel@localhost.localdomain> <20100822172548.GB8957@suse.de> <19570.38608.79434.179797@chiark.greenend.org.uk> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Mon, 23 Aug 2010 18:25:51 +0200 Message-ID: <1282580751.2605.1997.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 792 Lines: 18 On Mon, 2010-08-23 at 16:42 +0100, ijackson@chiark.greenend.org.uk wrote: > > mlocking the stack is entirely sensible and normal for a real-time > program. Most such programs use mlockall but there is no particular > reason why a program that has some more specific requirements should > use mlock to lock only a part of the stack. (Perhaps it has only one > real-time thread?) RT apps should pre-allocate and mlock their stack in advance (and pre-fault too for the paranoid). mlockall is a very bad interface and should really not be used. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/