From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759048AbcIPM6L (ORCPT ); Fri, 16 Sep 2016 08:58:11 -0400 Received: from mail-wm0-f53.google.com ([74.125.82.53]:38646 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752388AbcIPM6C (ORCPT ); Fri, 16 Sep 2016 08:58:02 -0400 Date: Fri, 16 Sep 2016 14:57:54 +0200 From: Ingo Molnar To: Josh Poimboeuf Cc: tip-bot for Andy Lutomirski , linux-tip-commits@vger.kernel.org, luto@kernel.org, hpa@zytor.com, dvlasenk@redhat.com, linux-kernel@vger.kernel.org, jann@thejh.net, peterz@infradead.org, torvalds@linux-foundation.org, brgerst@gmail.com, tglx@linutronix.de, bp@alien8.de Subject: Re: [tip:x86/asm] x86/dumpstack: Pin the target stack when dumping it Message-ID: <20160916125754.GA10184@gmail.com> References: <20160916115557.xsgxgjeefnsrrpct@treble> <20160916122816.lxfa3kmjukjevlrh@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916122816.lxfa3kmjukjevlrh@treble> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Josh Poimboeuf wrote: > On Fri, Sep 16, 2016 at 06:55:57AM -0500, Josh Poimboeuf wrote: > > On Fri, Sep 16, 2016 at 02:17:46AM -0700, tip-bot for Andy Lutomirski wrote: > > > Commit-ID: 1959a60182f48879635812a03a99c02231ea8677 > > > Gitweb: http://git.kernel.org/tip/1959a60182f48879635812a03a99c02231ea8677 > > > Author: Andy Lutomirski > > > AuthorDate: Thu, 15 Sep 2016 22:45:45 -0700 > > > Committer: Ingo Molnar > > > CommitDate: Fri, 16 Sep 2016 09:18:53 +0200 > > > > > > x86/dumpstack: Pin the target stack when dumping it > > > > > > Specifically, pin the stack in save_stack_trace_tsk() and > > > show_trace_log_lvl(). > > > > > > This will prevent a crash if the target task dies before or while > > > dumping its stack once we start freeing task stacks early. > > > > This causes a hang: > > The problem is that show_stack_log_lvl() can be called with a NULL > task_struct pointer to indicate 'current'. Could you please send a quick fix that addresses the hang by turning the NULL into 'current' or so? > No idea why that convention exists -- IMO we should just require the > caller to pass 'current' directly. For hysterical raisins I believe. It appears just a single caller passes non-current. Feel free to change this. Thanks, Ingo