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
| ||
|
Date: Fri, 11 Aug 2017 03:01:47 -0700 From: Christoph Hellwig <hch@...radead.org> To: Christoph Hellwig <hch@...radead.org>, linux-ext4@...r.kernel.org Subject: Re: [PATCH] ext4: introduce per-inode DAX flag On Tue, Aug 08, 2017 at 11:00:16AM +0200, Lukas Czerner wrote: > So I've read the thread where you talk about this. I do not see anything > about it being a masive mistake. I only see that you're confident that's > it's a wrong thing to do. Like you're ever not confident about > something;) Care to elaborate on what's wrong with it and why we do not > want it ? On the surface it does look like a usefull option to have. The problem is that DAX is an implementation detail on how to write data back. It has absolutely no user visible semantics. Encoding such a detail in the on-disk format is not a good idea.
Powered by blists - more mailing lists