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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 4 Nov 2021 09:17:40 +0100 From: Christoph Hellwig <hch@....de> To: Eric Sandeen <sandeen@...deen.net> Cc: Christoph Hellwig <hch@....de>, Dan Williams <dan.j.williams@...el.com>, Mike Snitzer <snitzer@...hat.com>, Ira Weiny <ira.weiny@...el.com>, dm-devel@...hat.com, linux-xfs@...r.kernel.org, nvdimm@...ts.linux.dev, linux-s390@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-erofs@...ts.ozlabs.org, linux-ext4@...r.kernel.org, virtualization@...ts.linux-foundation.org Subject: Re: futher decouple DAX from block devices On Wed, Nov 03, 2021 at 12:59:31PM -0500, Eric Sandeen wrote: > Christoph, can I ask what the end game looks like, here? If dax is completely > decoupled from block devices, are there user-visible changes? Yes. > If I want to > run fs-dax on a pmem device - what do I point mkfs at, if not a block device? The rough plan is to use the device dax character devices. I'll hopefully have a draft version in the next days.
Powered by blists - more mailing lists