Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932763AbbFWKK7 (ORCPT ); Tue, 23 Jun 2015 06:10:59 -0400 Received: from verein.lst.de ([213.95.11.211]:45954 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932677AbbFWKKv (ORCPT ); Tue, 23 Jun 2015 06:10:51 -0400 Date: Tue, 23 Jun 2015 12:10:49 +0200 From: Christoph Hellwig To: Jeff Moyer Cc: Christoph Hellwig , Dan Williams , Jens Axboe , "linux-nvdimm@lists.01.org" , "linux-kernel@vger.kernel.org" , Linux ACPI , linux-fsdevel , Ingo Molnar Subject: Re: [PATCH 14/15] libnvdimm: support read-only btt backing devices Message-ID: <20150623101049.GF24894@lst.de> References: <20150622072844.GA31263@lst.de> <20150622154138.GC7952@lst.de> <20150622163224.GA9168@lst.de> <20150622164804.GA9393@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 743 Lines: 14 On Mon, Jun 22, 2015 at 02:48:48PM -0400, Jeff Moyer wrote: > OK, so you think applications using buffered I/O will Just Work(TM)? My > guess is that things will start to break that hadn't broken in the > past. Sure, the application isn't designed properly, and that should be > fixed, but we shouldn't foist this on users as the default. They will work or break the same way as before. We have all kinds of cases of non-sector updates for buffered I/O anyway: inlіne data, tail merging, etc. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/