On Tue, Apr 21, 2020 at 08:45:39PM -0400, Sasha Levin wrote:
> On Tue, Apr 21, 2020 at 07:13:10PM +0200, gregkh@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx>.
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> > > From f3a99e761efa616028b255b4de58e9b5b87c5545 Mon Sep 17 00:00:00 2001
> > From: Tianyu Lan <Tianyu.Lan@xxxxxxxxxxxxx>
> > 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@xxxxxxxxxxxxx>
> > Reviewed-by: Michael Kelley <mikelley@xxxxxxxxxxxxx>
> > Link: https://lore.kernel.org/r/20200406155331.2105-7-Tianyu.Lan@xxxxxxxxxxxxx
> > Signed-off-by: Wei Liu <wei.liu@xxxxxxxxxx>
>
> 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
