[PATCH v11 0/4] Machine check recovery when kernel accesses poison

2016-02-17 Thread Tony Luck
[Resend of v11 with Boris' "Reviewed-by" tags added. For Ingo's workflow] -Tony Tony Luck (4): x86: Expand exception table to allow new handling options x86, mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries x86, mce: Add __mcsafe_copy() x86: Create a new syn

Re: [PATCH v11 0/4] Machine check recovery when kernel accesses poison

2016-02-11 Thread Borislav Petkov
On Thu, Feb 11, 2016 at 10:16:56PM +, Luck, Tony wrote: > > That's some changelog, I tell ya. Well, it took us long enough so for all 4: > > I'll see if Peter Jackson wants to turn it into a series of movies. LOL. A passing title might be "The Fellowship of the MCA"! :-) -- Regards/Gruss,

RE: [PATCH v11 0/4] Machine check recovery when kernel accesses poison

2016-02-11 Thread Luck, Tony
> That's some changelog, I tell ya. Well, it took us long enough so for all 4: I'll see if Peter Jackson wants to turn it into a series of movies. > Reviewed-by: Borislav Petkov Ingo: Boris is happy ... your turn to find things for me to fix (or is it ready for 4.6 now??) -Tony

Re: [PATCH v11 0/4] Machine check recovery when kernel accesses poison

2016-02-11 Thread Borislav Petkov
On Thu, Feb 11, 2016 at 01:34:10PM -0800, Tony Luck wrote: > This series is initially targeted at the folks doing filesystems > on top of NVDIMMs. They really want to be able to return -EIO > when there is a h/w error (just like spinning rust, and SSD does). > > I plan to use the same infrastructu

[PATCH v11 0/4] Machine check recovery when kernel accesses poison

2016-02-11 Thread Tony Luck
This series is initially targeted at the folks doing filesystems on top of NVDIMMs. They really want to be able to return -EIO when there is a h/w error (just like spinning rust, and SSD does). I plan to use the same infrastructure to write a machine check aware "copy_from_user()" that will SIGBUS