linux-ext4 - Re: [PATCH 3/3] ext2: remove dax EXPERIMENTAL warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YUq+P/5NG61CqszV@infradead.org>
Date:   Wed, 22 Sep 2021 06:25:19 +0100
From:   Christoph Hellwig <hch@...radead.org>
To:     "Darrick J. Wong" <djwong@...nel.org>
Cc:     Christoph Hellwig <hch@...radead.org>, Jan Kara <jack@...e.cz>,
        Eric Sandeen <sandeen@...hat.com>, linux-xfs@...r.kernel.org,
        linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        dan.j.williams@...el.com
Subject: Re: [PATCH 3/3] ext2: remove dax EXPERIMENTAL warning

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.