public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Michael Kelley <mikelley@microsoft.com>
Cc: mikelley@microsoft.com, linux-kernel@vger.kernel.org,
	kys@microsoft.com, sthemmin@microsoft.com, wei.liu@kernel.org,
	linux-hyperv@vger.kernel.org
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops
Date: Fri, 07 Aug 2020 11:06:47 +0200	[thread overview]
Message-ID: <87o8nmome0.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1596730935-11564-1-git-send-email-mikelley@microsoft.com>

Michael Kelley <mikelley@microsoft.com> writes:

> Hyper-V currently may be notified of a panic for any die event. But
> this results in false panic notifications for various user space traps
> that are die events. Fix this by ignoring die events that aren't oops.
>
> Fixes: 510f7aef65bb ("Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'")
> Signed-off-by: Michael Kelley <mikelley@microsoft.com>
> ---
>  drivers/hv/vmbus_drv.c | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index b50081c..910b6e9 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -86,6 +86,10 @@ static int hyperv_die_event(struct notifier_block *nb, unsigned long val,
>  	struct die_args *die = (struct die_args *)args;
>  	struct pt_regs *regs = die->regs;
>  
> +	/* Don't notify Hyper-V if the die event is other than oops */
> +	if (val != DIE_OOPS)
> +		return NOTIFY_DONE;
> +

Looking at die_val enum, DIE_PANIC also sounds like something we would
want to report but it doesn't get emitted anywhere and honestly I don't
quite understand how is was supposed to be different from DIE_OOPS.

Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>

>  	/*
>  	 * Hyper-V should be notified only once about a panic.  If we will be
>  	 * doing hyperv_report_panic_msg() later with kmsg data, don't do

-- 
Vitaly


  reply	other threads:[~2020-08-07  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 16:22 [PATCH 1/1] Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops Michael Kelley
2020-08-07  9:06 ` Vitaly Kuznetsov [this message]
2020-08-07 13:49   ` Wei Liu

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=87o8nmome0.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=sthemmin@microsoft.com \
    --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