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: Trigger crash enlightenment only once during" failed to apply to 4.19-stable tree
Date: Tue, 21 Apr 2020 20:38:57 -0400 [thread overview]
Message-ID: <20200422003857.GR1809@sasha-vm> (raw)
In-Reply-To: <1587489123120108@kroah.com>
On Tue, Apr 21, 2020 at 07:12:03PM +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 73f26e526f19afb3a06b76b970a76bcac2cafd05 Mon Sep 17 00:00:00 2001
>From: Tianyu Lan <Tianyu.Lan@microsoft.com>
>Date: Mon, 6 Apr 2020 08:53:28 -0700
>Subject: [PATCH] x86/Hyper-V: Trigger crash enlightenment only once during
> system crash.
>
>When a guest VM panics, Hyper-V should be notified only once via the
>crash synthetic MSRs. Current Linux code might write these crash MSRs
>twice during a system panic:
>1) hyperv_panic/die_event() calling hyperv_report_panic()
>2) hv_kmsg_dump() calling hyperv_report_panic_msg()
>
>Fix this by not calling hyperv_report_panic() if a kmsg dump has been
>successfully registered. The notification will happen later via
>hyperv_report_panic_msg().
>
>Fixes: 7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
>Reviewed-by: Michael Kelley <mikelley@microsoft.com>
>Signed-off-by: Tianyu Lan <Tianyu.Lan@microsoft.com>
>Link: https://lore.kernel.org/r/20200406155331.2105-4-Tianyu.Lan@microsoft.com
>Signed-off-by: Wei Liu <wei.liu@kernel.org>
This patch builds on 74347a99e73a ("x86/Hyper-V: Unload vmbus channel in
hv panic callback") which previously failed to apply. Once that issue
was resolved we can grab this patch too.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-04-22 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 17:12 FAILED: patch "[PATCH] x86/Hyper-V: Trigger crash enlightenment only once during" failed to apply to 4.19-stable tree gregkh
2020-04-22 0:38 ` Sasha Levin [this message]
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=20200422003857.GR1809@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).