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
Date: Wed, 22 Sep 2021 06:25:19 +0100 [thread overview]
Message-ID: <YUq+P/5NG61CqszV@infradead.org> (raw)
In-Reply-To: <20210922023622.GC570615@magnolia>
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.
next prev parent reply other threads:[~2021-09-22 5:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:22 [PATCH 0/3 RFC] Remove DAX experimental warnings Eric Sandeen
2021-09-15 17:22 ` [PATCH 1/3] xfs: remove dax EXPERIMENTAL warning Eric Sandeen
2021-09-15 18:54 ` Dan Williams
2021-09-15 17:22 ` [PATCH 2/3] ext4: " Eric Sandeen
2021-09-17 9:47 ` Jan Kara
2021-09-15 17:22 ` [PATCH 3/3] ext2: " Eric Sandeen
2021-09-17 9:47 ` Jan Kara
2021-09-17 12:59 ` Christoph Hellwig
2021-09-17 14:09 ` Eric Sandeen
2021-09-22 2:36 ` Darrick J. Wong
2021-09-22 5:25 ` Christoph Hellwig [this message]
2021-09-15 18:35 ` [PATCH 0/3 RFC] Remove DAX experimental warnings Dan Williams
2021-09-15 18:48 ` Eric Sandeen
2021-09-15 18:59 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YUq+P/5NG61CqszV@infradead.org \
--to=hch@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).