From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from imap.thunk.org ([74.207.234.97]:41638 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751868AbdH3PA1 (ORCPT ); Wed, 30 Aug 2017 11:00:27 -0400 Date: Wed, 30 Aug 2017 11:00:19 -0400 From: Theodore Ts'o Subject: Re: [PATCH] ext4: introduce per-inode DAX flag Message-ID: <20170830150019.cwrnum6zmrieqhdp@thunk.org> References: <20170825075415.GA748@infradead.org> <20170825151445.ycf5xomoxvebgaez@thunk.org> <20170825154032.GA1827@infradead.org> <20170825233358.GC17782@dastard> <20170828073853.GA23262@infradead.org> <20170828101014.GD17782@dastard> <20170829154922.GA24592@quack2.suse.cz> <20170829225717.GG10621@dastard> <20170830100059.GC28354@quack2.suse.cz> <20170830123450.GA14976@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170830123450.GA14976@infradead.org> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Christoph Hellwig Cc: Jan Kara , Dave Chinner , linux-ext4@vger.kernel.org, Lukas Czerner , linux-xfs@vger.kernel.org Bringing this discussion back to the "ext4: introduce per-inode DAX flag" patch, it sounds to me that I should _not_ apply this patch until we figure out to fix this for reals. Does this sound fair? If we think it's completely unfixable, then maybe XFS should consider (temporarily) withdrawing the per-file DAX support before there is a userspace and you have to support it forever, but that's between the NVM/dax and XFS folks to figure out. - Ted