generic/456 regression on 5.7-rc1, 1k test case

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm seeing consistent failures for generic/456 while running kvm-xfstests' 1k
test case on 5.7-rc1.  This is with an x86-64 test appliance root file system
image dated 23 March 2020.

The test fails when e2fsck reports "inconsistent fs: inode 12, i_size is
147456, should be 163840".

Bisecting 5.7-rc1 identified the following patch as the cause:
ext4: don't set dioread_nolock by default for blocksize < pagesize
(626b035b816b).  Reverting the patch in 5.7-rc1 reliably eliminates the test
failure.

Eric



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux