From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B632AC38A30 for ; Wed, 22 Apr 2020 06:09:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 890E32070B for ; Wed, 22 Apr 2020 06:09:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587535755; bh=XbTqVygLcXp8YaD9iX0uXfwFhBIKIv8fNc1T8TaYt38=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=MV1tpnQmzPrAWLf4pUJB7EyMN9T1j75C6X8H+xSue0u0zw1Rk1/xwKg7iJ7EXsXRt BcxSw6JD5lGlJEir4MO46r+0i3wMy30SA5cOv1JgsCXXm0KaXVyKCLRJhBkeLzWXV2 rp2ohx2VbpYKyhkj9ZU0nE6E4WGSNLZS39tnLXM4= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726071AbgDVGJP (ORCPT ); Wed, 22 Apr 2020 02:09:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:32994 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725912AbgDVGJP (ORCPT ); Wed, 22 Apr 2020 02:09:15 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DCF60206D9; Wed, 22 Apr 2020 06:09:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587535754; bh=XbTqVygLcXp8YaD9iX0uXfwFhBIKIv8fNc1T8TaYt38=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Zzxlek044swiWTiqdg836zittqb4emx5CoLXgkjAGQv0YJQVRjaepUrkK0rLpr38c zb8h+BESmQfwbST/8Jhh4s4YMv4fhFFbmj0EBu3y74r/RHMCj1IGpX1+27a3wAW8Ej UzZUF6MXCG0Ut/iyLtyAxlon9oPFZ62w/iirSRaU= Date: Wed, 22 Apr 2020 08:09:11 +0200 From: Greg KH To: Sasha Levin Cc: Tianyu.Lan@microsoft.com, mikelley@microsoft.com, wei.liu@kernel.org, stable@vger.kernel.org Subject: Re: FAILED: patch "[PATCH] x86/Hyper-V: Report crash data in die() when panic_on_oops is" failed to apply to 4.19-stable tree Message-ID: <20200422060911.GA2671421@kroah.com> References: <1587489190114108@kroah.com> <20200422004539.GT1809@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200422004539.GT1809@sasha-vm> Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Tue, Apr 21, 2020 at 08:45:39PM -0400, Sasha Levin wrote: > On Tue, Apr 21, 2020 at 07:13:10PM +0200, gregkh@linuxfoundation.org wrote: > > > > The patch below does not apply to the 4.19-stable tree. > > If someone wants it applied there, or to any other stable or longterm > > tree, then please email the backport, including the original git commit > > id to . > > > > thanks, > > > > greg k-h > > > > ------------------ original commit in Linus's tree ------------------ > > > > > From f3a99e761efa616028b255b4de58e9b5b87c5545 Mon Sep 17 00:00:00 2001 > > From: Tianyu Lan > > Date: Mon, 6 Apr 2020 08:53:31 -0700 > > Subject: [PATCH] x86/Hyper-V: Report crash data in die() when panic_on_oops is > > set > > > > When oops happens with panic_on_oops unset, the oops > > thread is killed by die() and system continues to run. > > In such case, guest should not report crash register > > data to host since system still runs. Check panic_on_oops > > and return directly in hyperv_report_panic() when the function > > is called in the die() and panic_on_oops is unset. Fix it. > > > > Fixes: 7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful") > > Signed-off-by: Tianyu Lan > > Reviewed-by: Michael Kelley > > Link: https://lore.kernel.org/r/20200406155331.2105-7-Tianyu.Lan@microsoft.com > > Signed-off-by: Wei Liu > > The additional conflicts here are due to missing suspend/resume and > header movement due to missing arm64 support. Fixed and queued up. Thanks for all of the FAILED fixups. greg k-h