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

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 the calling application when a syscall touches poison in user space (just like we do when the application touches the poison itself). I've dropped off the "reviewed-by" tags that I collected back prior to adding the new field to the exception table. Please send new ones if you can. Changes