From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753072AbcHOPfH (ORCPT ); Mon, 15 Aug 2016 11:35:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38900 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752856AbcHOPfF (ORCPT ); Mon, 15 Aug 2016 11:35:05 -0400 Date: Mon, 15 Aug 2016 10:34:58 -0500 From: Josh Poimboeuf To: Andy Lutomirski Cc: Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , X86 ML , "linux-kernel@vger.kernel.org" , Linus Torvalds , Steven Rostedt , Brian Gerst , Kees Cook , Peter Zijlstra , Frederic Weisbecker , Byungchul Park , Nilay Vaish Subject: Re: [PATCH v3 32/51] x86/dumpstack: simplify in_exception_stack() Message-ID: <20160815153458.7lochdewklrev3lz@treble> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Mon, 15 Aug 2016 15:35:05 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 14, 2016 at 12:48:15AM -0700, Andy Lutomirski wrote: > On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf wrote: > > in_exception_stack() does some bad, bad things just so the unwinder can > > print different values for different areas of the debug exception stack. > > > > There's no need to clarify where exactly on the stack it is. Just print > > "#DB" and be done with it. > > I'm okay with the printing part, but you're also using this to prevent > infinite looping. Will this cause the unwind to fail if we go debug > -> page fault -> debug or similar? Yes, but that behavior already existed. This patch doesn't change that; it just makes it clearer what's going on. -- Josh