From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Poimboeuf Subject: Re: [PATCH v4 14/16] x86/dumpstack/64: Handle faults when printing the "Stack:" part of an OOPS Date: Fri, 24 Jun 2016 10:36:18 -0500 Message-ID: <20160624153618.gbl2qzlbkapfbngs@treble> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55550 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750999AbcFXPgV (ORCPT ); Fri, 24 Jun 2016 11:36:21 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Andy Lutomirski Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Borislav Petkov , Nadav Amit , Kees Cook , Brian Gerst , "kernel-hardening@lists.openwall.com" , Linus Torvalds , Jann Horn , Heiko Carstens On Thu, Jun 23, 2016 at 09:23:09PM -0700, Andy Lutomirski wrote: > If we overflow the stack into a guard page, we'll recursively fault > when trying to dump the contents of the guard page. Use > probe_kernel_address so we can recover if this happens. > > Signed-off-by: Andy Lutomirski Reviewed-by: Josh Poimboeuf -- Josh