From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751132AbeEBIao (ORCPT ); Wed, 2 May 2018 04:30:44 -0400 Received: from mail.skyhub.de ([5.9.137.197]:59726 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750859AbeEBIan (ORCPT ); Wed, 2 May 2018 04:30:43 -0400 Date: Wed, 2 May 2018 10:30:21 +0200 From: Borislav Petkov To: Dan Williams Cc: Linus Torvalds , "linux-nvdimm@lists.01.org" , Tony Luck , Peter Zijlstra , the arch/x86 maintainers , Thomas Gleixner , Andy Lutomirski , Ingo Molnar , Al Viro , Andrew Morton , Linux Kernel Mailing List Subject: Re: [PATCH 0/6] use memcpy_mcsafe() for copy_to_iter() Message-ID: <20180502083021.GC2851@pd.tnic> References: <152520750404.36522.15462513519590065300.stgit@dwillia2-desk3.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 01, 2018 at 07:25:57PM -0700, Dan Williams wrote: > Right, but the only way to make MCE non-fatal is to teach the machine > check handler about recoverable conditions. This patch teaches the > machine check handler how to recover copy_to_iter() errors. Yeah, about that: maybe we talked about this at the time but does the actual MCE signature state the error was caused by a read from an nvdimm range? Because if so, we could lower the severity of the error when we look at it in the #MC handler and do some more graceful handling later... -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.