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: Wed, 30 Aug 2017 11:00:19 -0400 From: Theodore Ts'o <tytso@....edu> To: Christoph Hellwig <hch@...radead.org> Cc: Jan Kara <jack@...e.cz>, Dave Chinner <david@...morbit.com>, linux-ext4@...r.kernel.org, Lukas Czerner <lczerner@...hat.com>, linux-xfs@...r.kernel.org Subject: Re: [PATCH] ext4: introduce per-inode DAX flag Bringing this discussion back to the "ext4: introduce per-inode DAX flag" patch, it sounds to me that I should _not_ apply this patch until we figure out to fix this for reals. Does this sound fair? If we think it's completely unfixable, then maybe XFS should consider (temporarily) withdrawing the per-file DAX support before there is a userspace and you have to support it forever, but that's between the NVM/dax and XFS folks to figure out. - Ted
Powered by blists - more mailing lists