Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932686Ab3GET1x (ORCPT ); Fri, 5 Jul 2013 15:27:53 -0400 Received: from mail-ve0-f176.google.com ([209.85.128.176]:45828 "EHLO mail-ve0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752054Ab3GET1w (ORCPT ); Fri, 5 Jul 2013 15:27:52 -0400 MIME-Version: 1.0 In-Reply-To: <20130705065113.GA6588@gmail.com> References: <20130704015525.GA8486@redhat.com> <51D5BA25.9060207@zytor.com> <20130705065113.GA6588@gmail.com> Date: Fri, 5 Jul 2013 12:27:51 -0700 X-Google-Sender-Auth: ySGBVVHsY6383b5IiQR_MLYNias Message-ID: Subject: Re: scheduling while atomic & hang. From: Linus Torvalds To: Ingo Molnar Cc: "H. Peter Anvin" , =?UTF-8?B?RnLDqWTDqXJpYyBXZWlzYmVja2Vy?= , Dave Jones , Linux Kernel , Thomas Gleixner Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 19 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 -- 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/