From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [PATCH 14/15] libnvdimm: support read-only btt backing devices Date: Mon, 22 Jun 2015 11:02:24 -0400 Message-ID: References: <20150617235209.12943.24419.stgit@dwillia2-desk3.amr.corp.intel.com> <20150617235602.12943.24958.stgit@dwillia2-desk3.amr.corp.intel.com> <20150621101346.GF5915@lst.de> <20150621135406.GA9572@lst.de> <20150622063028.GA30434@lst.de> <20150622072844.GA31263@lst.de> Mime-Version: 1.0 Content-Type: text/plain Cc: Christoph Hellwig , Jens Axboe , "linux-nvdimm\@lists.01.org" , "linux-kernel\@vger.kernel.org" , Linux ACPI , linux-fsdevel , Ingo Molnar To: Dan Williams Return-path: Received: from mx1.redhat.com ([209.132.183.28]:56031 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751183AbbFVPC0 (ORCPT ); Mon, 22 Jun 2015 11:02:26 -0400 In-Reply-To: (Dan Williams's message of "Mon, 22 Jun 2015 00:39:34 -0700") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Dan Williams writes: >> Sounds like we simply shouldn't merge btt at all for now and wait for >> a real use case, which would simplify the whole issue a lot. > > The sinister aspect of sector tearing is that most applications don't > know they have this dependency. At least today's disk's rarely ever > tear sectors and if they do you almost certainly get a CRC error on > access. NVDIMMs will always tear and always silently. I think not > merging BTT at all to see what happens is simply wrong. Agreed, we can't audit all code, and springing this potential data corruptor on people seems irresponsible. -Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in