Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753063AbbBRANW (ORCPT ); Tue, 17 Feb 2015 19:13:22 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:37612 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752198AbbBRANV (ORCPT ); Tue, 17 Feb 2015 19:13:21 -0500 Date: Tue, 17 Feb 2015 16:13:20 -0800 From: Andrew Morton To: Josh Poimboeuf Cc: Ingo Molnar , Peter Zijlstra , Jiri Kosina , Seth Jennings , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/3] stacktrace: add save_stack_trace_tsk_safe() Message-Id: <20150217161320.fb3da954106ad44e9f07ca9e@linux-foundation.org> In-Reply-To: References: X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 815 Lines: 18 On Mon, 16 Feb 2015 12:52:35 -0600 Josh Poimboeuf wrote: > It isn't possible to get the stack of a running task (other than > current) because we don't have the stack pointer and the stack can be > inconsistent anyway. Add a safe stack saving facility which only saves > the stack of the task if it's sleeping or if it's the current task. Can you send the task an IPI and get it to save its stack for you? There's probably some (messy, arch-dependent) way of trimming away the interrupt-related stuff off the stack, if that's really needed. -- 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/