| 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
| ||
|
Message-ID: <20151025204101.GH19199@dastard> Date: Mon, 26 Oct 2015 07:41:01 +1100 From: Dave Chinner <david@...morbit.com> To: Jan Kara <jack@...e.cz> Cc: linux-ext4@...r.kernel.org, fstests@...r.kernel.org Subject: Re: Test ext4/001 On Thu, Oct 22, 2015 at 11:10:17AM +0200, Jan Kara wrote: > Hi, > > I've checked why test ext4/001 fails for me with DAX and after some > investigation I've realized that the test assumes that > extent_max_zeroout_kb is 32 KB and thus unwritten extent will get converted > to written as a whole and not split. With DAX that doesn't happen (because > of difference between EXT4_GET_BLOCKS_ flags passed in writeback path and > DAX write path) and so the result differs. > > So I was wondering how to best fix this. Either we could switch > extent_max_zeroout_kb to 0 to make the result same (but that has a slight > disadvantage that we would lose testing of the zeroout logic) or we could > increase file size so that zeroout doesn't trigger or something else? > Anyone has some idea? Generic tests that have this problem with ext4 turn set zeroout to 0. You could always just filter the mount options to remove DAX from this test - filtering mount options is not uncommon in XFS specific tests that are designed to test specific functionality that may be incompatible with the provided mount options. Cheers, Dave. -- Dave Chinner david@...morbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists