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: Wed, 3 Nov 2021 12:59:31 -0500 From: Eric Sandeen <sandeen@...deen.net> To: Christoph Hellwig <hch@....de> Cc: 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 10/17/21 11:40 PM, Christoph Hellwig wrote: > Hi Dan, > > this series cleans up and simplifies the association between DAX and block > devices in preparation of allowing to mount file systems directly on DAX > devices without a detour through block devices. Christoph, can I ask what the end game looks like, here? If dax is completely decoupled from block devices, are there user-visible changes? If I want to run fs-dax on a pmem device - what do I point mkfs at, if not a block device? Thanks, -Eric
Powered by blists - more mailing lists