Received: by 10.223.176.5 with SMTP id f5csp4077294wra; Tue, 30 Jan 2018 01:37:29 -0800 (PST) X-Google-Smtp-Source: AH8x224rsv53+lSiQDnokPDb/9hQYW1GMBbBsLs/WmOvRtu9HbgQq8K81Q9ZdrSM4LuzdWh1sNU6 X-Received: by 2002:a17:902:2823:: with SMTP id e32-v6mr22753399plb.44.1517305049232; Tue, 30 Jan 2018 01:37:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517305049; cv=none; d=google.com; s=arc-20160816; b=jVLsBdeIsS7Bea7UzyHcfbBveTa5/3Pt7hwiTbiiN3AWWpN1HDCe6r9+0qINNIzyEK QAQNO/FJNdx5pBIE5M22bAZ7sRMot+L7l/wkvqSrPpLP1ODlDFOYkm/wbhvdxteVdZG7 88d9aLtLPnd3CS/kSYVwPmG1TeMd549DlUl1lhxTfXQReYsFU7dZJL1u3t9mIzpOPDD9 6g1cGJED9/y33htb2bHoE5zwSyUUx2vj4hQ9veNmyfOtfuApp3kG+xZ8jPbVj/ATtq1N gTFhDLhDfW8FEXqh0qcrNb4dijIbmyw75d38IXmDvb+R/Icipxwy7QRSskt03I+8H+PT IRTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=xJIwFb3g4nKZTCF+kLyZ1810McSTu4xGGZaURXelodY=; b=KxgumNtA/MY2rLnCgRPqGm1mtJzJx54Xsc2sKSvvRxNzZYbFRElHRMRwq/IfehfuF7 RPvfIL6wfAMUn1Qyssc9G0dG5qhTVX2oFJwICX+Rxw16xmJ+6ClzDdQB9d+1yJKb+gyG GMtaKrLIdjq5LuA4e/k0gMnsa8B8z3jo+cZJoVIlqrprwfxrnZHjnkRN/VIVjIK5yBlA T5O9HI7raVH+exQmXW+S6gsAJM6S+kAAK6/BT96Q5NgsfhUpsHKz0Rovn6BivH3IogDE 2d4oCszQwsTJfwybteGfJWkuBWqENFzKI/3PJ1jT1q/NH3ZdSqRqLQKGUOGuzBgXwaT1 ok8A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 94-v6si2832444plb.807.2018.01.30.01.37.14; Tue, 30 Jan 2018 01:37:29 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751611AbeA3Jgp (ORCPT + 99 others); Tue, 30 Jan 2018 04:36:45 -0500 Received: from mx2.suse.de ([195.135.220.15]:36520 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751262AbeA3Jgm (ORCPT ); Tue, 30 Jan 2018 04:36:42 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 2033AAD2D; Tue, 30 Jan 2018 09:36:41 +0000 (UTC) Date: Tue, 30 Jan 2018 10:36:40 +0100 From: Petr Mladek To: Dave Young Cc: Sergey Senozhatsky , Steven Rostedt , Andi Kleen , sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, kexec@lists.infradead.org Subject: Re: [PATCH V2] print kdump kernel loaded status in stack dump Message-ID: <20180130093640.r4a45m6eicmyeljc@pathway.suse.cz> References: <20180127041129.GA29016@dhcp-128-65.nay.redhat.com> <20180130085055.GA569@jagdpanzerIV> <20180130090729.GA2558@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180130090729.GA2558@dhcp-128-65.nay.redhat.com> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 2018-01-30 17:07:29, Dave Young wrote: > On 01/30/18 at 05:50pm, Sergey Senozhatsky wrote: > > On (01/27/18 12:11), Dave Young wrote: > > > It is useful to print kdump kernel loaded status in dump_stack() > > > especially when panic happens so that we can differenciate > > > kdump kernel early hang and a normal panic in a bug report. > > > > > > Signed-off-by: Dave Young > > > > Looks OK to me. > > > > Reviewed-by: Sergey Senozhatsky Same here: Reviewed-by: Petr Mladek > > I agree with Steven, would be better to move the whole thing > > to lib/dump_stack.c > > If nobody has plan I can put it in my todo list, probably do it next > week. Sounds good. JFYI, I would target these changes for 4.17. There was some discussion about where and how to show the new information. IMHO, it would deserve some gurgling in linux-next. Best Regards, Petr