Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752840Ab3GFICi (ORCPT ); Sat, 6 Jul 2013 04:02:38 -0400 Received: from mail-ee0-f53.google.com ([74.125.83.53]:38203 "EHLO mail-ee0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752590Ab3GFICf (ORCPT ); Sat, 6 Jul 2013 04:02:35 -0400 Date: Sat, 6 Jul 2013 10:02:27 +0200 From: Frederic Weisbecker To: Linus Torvalds Cc: Ingo Molnar , "H. Peter Anvin" , Dave Jones , Linux Kernel , Thomas Gleixner Subject: Re: scheduling while atomic & hang. Message-ID: <20130706080225.GA439@somewhere> References: <20130704015525.GA8486@redhat.com> <51D5BA25.9060207@zytor.com> <20130705065113.GA6588@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1099 Lines: 24 On Fri, Jul 05, 2013 at 12:27:51PM -0700, Linus Torvalds wrote: > On Thu, Jul 4, 2013 at 11:51 PM, Ingo Molnar wrote: > > > > It would be nice to have a full-kernel-stack backtrace printout as an > > option, which prints entries 'above' the current RSP. > > One problem with that is that it is likely to be mostly overwritten by > the debug code that is about to print this all out - and any non-debug > code may well be really old, just with a sufficiently deep stack trace > to show up. Not to mention missing any irq-stack changes etc anyway. > > So it can easily be *very* misleading - I'm not sure how useful it > would be as an idea. > > Linus So if the unwider doesn't run with the same stak than the target, it migh work. This can work with BUG for example But I believe that WARN doesn't do a trap in x86. -- 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/