From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pg0-x243.google.com ([2607:f8b0:400e:c05::243]) by bombadil.infradead.org with esmtps (Exim 4.89 #1 (Red Hat Linux)) id 1egRdG-0001n4-He for kexec@lists.infradead.org; Tue, 30 Jan 2018 08:51:15 +0000 Received: by mail-pg0-x243.google.com with SMTP id m20so6708431pgc.11 for ; Tue, 30 Jan 2018 00:50:59 -0800 (PST) Date: Tue, 30 Jan 2018 17:50:55 +0900 From: Sergey Senozhatsky Subject: Re: [PATCH V2] print kdump kernel loaded status in stack dump Message-ID: <20180130085055.GA569@jagdpanzerIV> References: <20180127041129.GA29016@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20180127041129.GA29016@dhcp-128-65.nay.redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Dave Young Cc: Petr Mladek , Andi Kleen , kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Steven Rostedt , sergey.senozhatsky@gmail.com, akpm@linux-foundation.org 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 I agree with Steven, would be better to move the whole thing to lib/dump_stack.c -ss _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751774AbeA3IvB (ORCPT ); Tue, 30 Jan 2018 03:51:01 -0500 Received: from mail-pg0-f67.google.com ([74.125.83.67]:38994 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751296AbeA3Iu7 (ORCPT ); Tue, 30 Jan 2018 03:50:59 -0500 X-Google-Smtp-Source: AH8x225afoLwEXv4MIp1M4Paw6vMDiixHpzTKpgCY5X0fMD8HVTFxXbszwNsLFP76JZ/eiLamvKEHw== Date: Tue, 30 Jan 2018 17:50:55 +0900 From: Sergey Senozhatsky To: Dave Young Cc: Petr Mladek , 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: <20180130085055.GA569@jagdpanzerIV> References: <20180127041129.GA29016@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180127041129.GA29016@dhcp-128-65.nay.redhat.com> User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 I agree with Steven, would be better to move the whole thing to lib/dump_stack.c -ss