From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Sat, 28 Feb 2009 17:54:09 +0000 (GMT) Received: from casper.infradead.org ([85.118.1.10]:14032 "EHLO casper.infradead.org") by ftp.linux-mips.org with ESMTP id S20809011AbZB1RyH (ORCPT ); Sat, 28 Feb 2009 17:54:07 +0000 Received: from c-67-170-138-156.hsd1.or.comcast.net ([67.170.138.156] helo=localhost.localdomain) by casper.infradead.org with esmtpsa (Exim 4.69 #1 (Red Hat Linux)) id 1LdTNw-0000xv-Cd; Sat, 28 Feb 2009 17:54:00 +0000 Date: Sat, 28 Feb 2009 09:54:33 -0800 From: Arjan van de Ven To: Greg KH Cc: Linus Torvalds , Roland McGrath , linux-mips@linux-mips.org, x86@kernel.org, linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, sparclinux@vger.kernel.org, Andrew Morton , stable@kernel.org Subject: Re: [stable] [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole Message-ID: <20090228095433.6af07a89@infradead.org> In-Reply-To: <20090228174601.GB27607@kroah.com> References: <20090228030226.C0D34FC3DA@magilla.sf.frob.com> <20090228030413.5B915FC3DA@magilla.sf.frob.com> <20090228072554.CFEA6FC3DA@magilla.sf.frob.com> <20090228174601.GB27607@kroah.com> Organization: Intel X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 21986 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: arjan@infradead.org Precedence: bulk X-list: linux-mips On Sat, 28 Feb 2009 09:46:01 -0800 Greg KH wrote: > On Sat, Feb 28, 2009 at 09:23:36AM -0800, Linus Torvalds wrote: > > On Fri, 27 Feb 2009, Roland McGrath wrote: > > > But here is the patch you asked for. > > > > Yes, this looks much more straightforward. > > > > And I guess the seccomp interaction means that this is potentially > > a 2.6.29 thing. Not that I know whether anybody actually _uses_ > > seccomp. It does seem to be enabled in at least Fedora kernels, but > > it might not be used anywhere. > > It's enabled in SuSE kernels. > but are there users of it? I thought Andrea stopped the cpushare thing that was the only user of this.... -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org