From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x244.google.com (mail-oi1-x244.google.com [IPv6:2607:f8b0:4864:20::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id E4BB2211350C4 for ; Tue, 6 Nov 2018 10:02:58 -0800 (PST) Received: by mail-oi1-x244.google.com with SMTP id p144-v6so11487397oic.12 for ; Tue, 06 Nov 2018 10:02:58 -0800 (PST) MIME-Version: 1.0 References: <20181026003729.8420-1-vishal.l.verma@intel.com> <20181026003729.8420-2-vishal.l.verma@intel.com> <20181106145137.GJ13712@zn.tnic> <20181106175341.GK13712@zn.tnic> In-Reply-To: <20181106175341.GK13712@zn.tnic> From: Dan Williams Date: Tue, 6 Nov 2018 10:02:46 -0800 Message-ID: Subject: Re: [PATCH v3 2/2] nfit, mce: validate the mce->addr before using it List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Borislav Petkov Cc: "Luck, Tony" , linux-nvdimm , stable , linux-edac@vger.kernel.org List-ID: On Tue, Nov 6, 2018 at 9:53 AM Borislav Petkov wrote: > > On Tue, Nov 06, 2018 at 08:20:38AM -0800, Dan Williams wrote: > > I recommended the split so the fixes can be tracked and / or reverted > > independently if they cause problems. > > Do you have anything concrete in mind that might go wrong or just a > general cautiousness? Just general cautiousness, I'm not opposed to squashing them. > Or do you think the hw might not spit what mce_usable_address() is > checking for, for NVDIMM MCEs, so that you'd like to be able to revert > that second patch? mce_usable_address() should not have any sensitivity to NVDIMM vs DRAM MCEs. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm