Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 22 Sep 2021 06:25:19 +0100
From:   Christoph Hellwig <hch@infradead.org>
To:     "Darrick J. Wong" <djwong@kernel.org>
Cc:     Christoph Hellwig <hch@infradead.org>, Jan Kara <jack@suse.cz>,
        Eric Sandeen <sandeen@redhat.com>, linux-xfs@vger.kernel.org,
        linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
        dan.j.williams@intel.com
Subject: Re: [PATCH 3/3] ext2: remove dax EXPERIMENTAL warning
Message-ID: <YUq+P/5NG61CqszV@infradead.org>
References: <1631726561-16358-1-git-send-email-sandeen@redhat.com>
 <1631726561-16358-4-git-send-email-sandeen@redhat.com>
 <20210917094707.GD6547@quack2.suse.cz>
 <YUSRHjynaozAuO+P@infradead.org>
 <20210922023622.GC570615@magnolia>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210922023622.GC570615@magnolia>
Precedence: bulk

On Tue, Sep 21, 2021 at 07:36:22PM -0700, Darrick J. Wong wrote:
> 'still a mess' isn't all that useful for figuring out what still needs
> to be done and splitting up the work.  Do you have items beyond my own
> list below?
> 
>  - still arguing over what exactly FALLOC_FL_ZERO_REINIT_WHATEVER_PONIES
>    should be doing
>  - no reflink support, encompassing:
>  - hwpoison from mmap regions really ought to tell the fs that bad stuff
>    happened
>  - mm rmap can't handle more than one owner

My main really big item is that we're still mounting through a fake
block device, suporting partitions and all that crap.  We need to sort
out the whole story of how pmem/nvdimm is actually treated, because
what we have right now is not sustainable at all.