From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
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
Date: Tue, 21 Apr 2020 20:45:39 -0400 [thread overview]
Message-ID: <20200422004539.GT1809@sasha-vm> (raw)
In-Reply-To: <1587489190114108@kroah.com>
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 <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From f3a99e761efa616028b255b4de58e9b5b87c5545 Mon Sep 17 00:00:00 2001
>From: Tianyu Lan <Tianyu.Lan@microsoft.com>
>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 <Tianyu.Lan@microsoft.com>
>Reviewed-by: Michael Kelley <mikelley@microsoft.com>
>Link: https://lore.kernel.org/r/20200406155331.2105-7-Tianyu.Lan@microsoft.com
>Signed-off-by: Wei Liu <wei.liu@kernel.org>
The additional conflicts here are due to missing suspend/resume and
header movement due to missing arm64 support. Fixed and queued up.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-04-22 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 17:13 FAILED: patch "[PATCH] x86/Hyper-V: Report crash data in die() when panic_on_oops is" failed to apply to 4.19-stable tree gregkh
2020-04-22 0:45 ` Sasha Levin [this message]
2020-04-22 6:09 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200422004539.GT1809@sasha-vm \
--to=sashal@kernel.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=mikelley@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=wei.liu@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.