From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751916AbcBKWC3 (ORCPT ); Thu, 11 Feb 2016 17:02:29 -0500 Received: from mail.skyhub.de ([78.46.96.112]:45154 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751549AbcBKWC2 (ORCPT ); Thu, 11 Feb 2016 17:02:28 -0500 Date: Thu, 11 Feb 2016 23:02:22 +0100 From: Borislav Petkov To: Tony Luck Cc: Ingo Molnar , Andrew Morton , Andy Lutomirski , Dan Williams , elliott@hpe.com, Brian Gerst , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@ml01.01.org, x86@kernel.org Subject: Re: [PATCH v11 0/4] Machine check recovery when kernel accesses poison Message-ID: <20160211220222.GJ5565@pd.tnic> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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 That's some changelog, I tell ya. Well, it took us long enough so for all 4: Reviewed-by: Borislav Petkov -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.