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 18:35:59 +0100 From: Christoph Hellwig <hch@....de> To: "Darrick J. Wong" <djwong@...nel.org> Cc: Christoph Hellwig <hch@....de>, Eric Sandeen <sandeen@...deen.net>, 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 Thu, Nov 04, 2021 at 10:34:17AM -0700, Darrick J. Wong wrote: > /me wonders, are block devices going away? Will mkfs.xfs have to learn > how to talk to certain chardevs? I guess jffs2 and others already do > that kind of thing... but I suppose I can wait for the real draft to > show up to ramble further. ;) Right now I've mostly been looking into the kernel side. An no, I do not expect /dev/pmem* to go away as you'll still need it for a not DAX aware file system and/or application (such as mkfs initially). But yes, just pointing mkfs to the chardev should be doable with very little work. We can point it to a regular file after all.
Powered by blists - more mailing lists