Comment 4 for bug 1891222

SRU Template
------------

[Impact]

Currently, Hyper-V may be notified of a panic for any die event.

However, this results in false panic notifications for various user
space traps that are die events.

The following commit fixes this by ignoring die events that is not an
oops:

608a973bd52e ("Drivers: hv: vmbus: Only notify Hyper-V for die events
that are oops")

[Test Case]

Without the fix in the Linux VM, do the following to demonstrate the
problem:

1. Create a VM in Azure.
2. Run a user space program that does a divide-by-zero. The user space
   program will terminate abnormally because of the error.
3. Monitor notifications in the Azure portal in the Resource Health
   section of the VM. There should be a report that the Linux VM has
   panicked.

With the fix, do the same steps. The panic report in Step #3 should not
happen.

[Regression Potential]

The risk of regression is low. This patch fixes the issue by ignoring
die events that aren't oops.

The upstream LKML thread mentions that DIE_PANIC may also be something
that should be reported, but it doesn't get emitted anywhere so this
might not be significantly different than DIE_OOPS.