Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752222Ab3HUPcP (ORCPT ); Wed, 21 Aug 2013 11:32:15 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:42321 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751708Ab3HUPcO (ORCPT ); Wed, 21 Aug 2013 11:32:14 -0400 Date: Wed, 21 Aug 2013 16:26:14 +0100 From: Russell King - ARM Linux To: Dave Jones Cc: Aaro Koskinen , ksummit-2013-discuss@lists.linuxfoundation.org, Kees Cook , "linux-arm-kernel@lists.infradead.org" , LKML Subject: Re: [Ksummit-2013-discuss] [ARM ATTEND] catching up on exploit mitigations Message-ID: <20130821152614.GN17845@n2100.arm.linux.org.uk> References: <20130730221435.GA22240@redhat.com> <20130730231120.GC30725@blackmetal.musicnaut.iki.fi> <20130730231533.GA26824@redhat.com> <20130730235834.GD30725@blackmetal.musicnaut.iki.fi> <20130731000444.GC1281@redhat.com> <20130731094012.GU24642@n2100.arm.linux.org.uk> <20130731142430.GA4545@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130731142430.GA4545@redhat.com> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1435 Lines: 26 On Wed, Jul 31, 2013 at 10:24:30AM -0400, Dave Jones wrote: > On Wed, Jul 31, 2013 at 10:40:12AM +0100, Russell King - ARM Linux wrote: > > On Tue, Jul 30, 2013 at 08:04:44PM -0400, Dave Jones wrote: > > > To use ARM as an example, the bugs I've seen have mostly been in arch specific > > > code that does things like page-table manipulation. The chromebook bugs I > > > was hitting for eg were various kinds of PTE corruption warnings. > > > > Hmm, really? Did you reported these bugs? I'm not aware of mainline > > having any changes related to bug reports on PTEs on ARM. > > I wasn't sure if it was a googleism, or happens on mainline, so no. I've been running several iterations of it for a while (== up to 10 minutes run time - which is normally about how long it takes to find the rather-too- exposed kmalloc in sys_oabi_epoll_wait) and so far have seen no sign of any page table corruption. Maybe you can give some ideas as to how you were running it? Was it running as root or as a normal user? Were there any nonstandard platform specific devices in /dev which that user could access - such as graphics or video decoder devices which could be exposing big holes? -- 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/