Best way to debug an invalid opcode

[Rik van Riel]

On Thu, 2020-03-19 at 10:22 +0100, Karaoui mohamed lamine wrote:
> Hi list,
> 
> I am currently encountering a kernel oops that indicate an "invalid
> opcode: 0000 [#1] SMP"
> 
> I am working on this project https://github.com/GiantVM/Linux-DSM
> 
> The full log of the bug can be found here: 
> https://github.com/GiantVM/Linux-DSM/pull/3 (at the end)
> 
> Here is a snippet of the log:
> [  107.980285] ------------[ cut here ]------------
> [  107.980995] kernel BUG at arch/x86/kvm/dsm-util.c:214!

Why don't you look at the code?

https://github.com/GiantVM/Linux-DSM/blob/master/arch/x86/kvm/dsm-util.c#L214

This bug is in the DSM code itself. You'll have to figure
out why xbzrle_decode_buffer is returning a negative value.

-- 
All Rights Reversed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20200319/a2c11170/attachment.sig>