linux-kernel - xfstests failures with xfs, dax and v4.4-rc3

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 2 Dec 2015 11:34:38 -0700
From:	Ross Zwisler <ross.zwisler@...ux.intel.com>
To:	Dave Chinner <david@...morbit.com>, xfs@....sgi.com,
	Brian Foster <bfoster@...hat.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	Jeff Moyer <jmoyer@...hat.com>
Subject: xfstests failures with xfs, dax and v4.4-rc3

I'm hitting a few more test failures in my testing setup with v4.4-rc3, xfs
and DAX.  My test setup is a pair of 4GiB PMEM partitions in a KVM virtual
machine.  Here are the failures:

# ./check generic/256 generic/274 xfs/041
FSTYP         -- xfs (debug)
PLATFORM      -- Linux/x86_64 alara 4.4.0-rc3
MKFS_OPTIONS  -- -f -bsize=4096 /dev/pmem0p2
MOUNT_OPTIONS -- -o dax -o context=system_u:object_r:nfs_t:s0 /dev/pmem0p2 /mnt/xfstests_scratch

generic/256 43s ... - output mismatch (see /root/xfstests/results//generic/256.out.bad)
    --- tests/generic/256.out	2015-10-02 10:19:36.807795900 -0600
    +++ /root/xfstests/results//generic/256.out.bad	2015-12-02 11:22:34.838845475 -0700
    @@ -1 +1,500 @@
     QA output created by 256
    +fallocate: No space left on device
    +fallocate: No space left on device
    +fallocate: No space left on device
    +fallocate: No space left on device
    +fallocate: No space left on device
    +fallocate: No space left on device
    ...
    (Run 'diff -u tests/generic/256.out /root/xfstests/results//generic/256.out.bad'  to see the entire diff)
generic/274 7s ... [failed, exit status 1] - output mismatch (see /root/xfstests/results//generic/274.out.bad)
    --- tests/generic/274.out	2015-10-02 10:19:36.808795907 -0600
    +++ /root/xfstests/results//generic/274.out.bad	2015-12-02 11:22:37.656868990 -0700
    @@ -2,4 +2,5 @@
     ------------------------------
     preallocation test
     ------------------------------
    -done
    +failed to write to test file
    +(see /root/xfstests/results//generic/274.full for details)
    ...
    (Run 'diff -u tests/generic/274.out /root/xfstests/results//generic/274.out.bad'  to see the entire diff)
xfs/041 14s ... [failed, exit status 1] - output mismatch (see /root/xfstests/results//xfs/041.out.bad)
    --- tests/xfs/041.out	2015-10-02 10:19:36.818795975 -0600
    +++ /root/xfstests/results//xfs/041.out.bad	2015-12-02 11:22:42.553909854 -0700
    @@ -4,16 +4,5 @@
     Grow filesystem to 33m... done
     Flush filesystem... done
     Check files... done
    -Fill filesystem... done
    -Grow filesystem to 67m... done
    -Flush filesystem... done
    -Check files... done
    ...
    (Run 'diff -u tests/xfs/041.out /root/xfstests/results//xfs/041.out.bad'  to see the entire diff)
Ran: generic/256 generic/274 xfs/041
Failures: generic/256 generic/274 xfs/041
Failed 3 of 3 tests

The .bad files are attached to this mail.

These three tests pass 100% of the time with and without DAX using v4.3, pass
100% of the time with v4.4-rc3 without DAX, and fail 100% of the time with
v4.4-rc3 with DAX enabled.

I did try doubling the size of my ramdisk partition to see if that made any
difference, and the failure was still present.

I'm using xfsprogs v4.3.0.

Please let me know if you have any other questions about how to reproduce the
failure.  I'm also happy to test patches.

Thanks,
- Ross

View attachment "041.out.bad" of type "text/plain" (402 bytes)

View attachment "256.out.bad" of type "text/plain" (17490 bytes)

View attachment "274.out.bad" of type "text/plain" (195 bytes)