From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754337AbdDLMuC (ORCPT ); Wed, 12 Apr 2017 08:50:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55182 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754286AbdDLMty (ORCPT ); Wed, 12 Apr 2017 08:49:54 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com DA00480483 Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jmoyer@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com DA00480483 From: Jeff Moyer To: Dan Williams Cc: linux-nvdimm@ml01.01.org, Vishal Verma , Dave Jiang , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v2] libnvdimm: fix btt vs clear poison locking References: <149195214773.14530.8851419580700446789.stgit@dwillia2-desk3.amr.corp.intel.com> X-PGP-KeyID: 1F78E1B4 X-PGP-CertKey: F6FE 280D 8293 F72C 65FD 5A58 1FF8 A7CA 1F78 E1B4 X-PCLoadLetter: What the f**k does that mean? Date: Wed, 12 Apr 2017 08:49:52 -0400 In-Reply-To: <149195214773.14530.8851419580700446789.stgit@dwillia2-desk3.amr.corp.intel.com> (Dan Williams's message of "Tue, 11 Apr 2017 16:10:58 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 12 Apr 2017 12:49:54 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dan Williams writes: > As a minimal fix, disable error clearing when the BTT is enabled for the > namespace. For the final fix a larger rework of the poison list locking > is needed. I think "fix" is a strong word for this patch. ;-) Looks fine, though. Reviewed-by: Jeff Moyer