Re: [RFC PATCH 0/3] Machine check recovery when kernel accesses poison

Borislav Petkov
2015-11-11T22:28:52Z

On Wed, Nov 11, 2015 at 01:48:04PM -0800, Luck, Tony wrote:
> No flag. We can search MCi_ADDR across the ranges to see whether this
> was a normal RAM error on non-volatile. But that doesn't make this patch
> moot. We still need to change the return address to go to the fixup code
> instead of back to the place where we hit the error.

Why?

If you know that it is in the nvdimm range, you can grade the error with
lower severity...

Or do you mean that without the exception table we'll return back to the
insn causing the error and loop indefinitely this way?

--
Regards/Gruss,
Boris.

ECO tip #101: Trim your mails when you reply.