Filipe Manana 5a3ce97e3e generic: add test for fsync after creating hard link ...

This test is motivated by an fsync issue discovered in btrfs.
The issue was that we could lose file data, that was previously
fsync'ed successfully, if we end up adding a hard link to our
inode and then persist the fsync log later via an fsync of other
inode for example.

The btrfs issue was fixed by the following linux kernel patch:

  Btrfs: fix fsync data loss after adding hard link to inode

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>

2015-02-16 10:13:27 +11:00

..

btrfs

btrfs: add regression test for remount with thread_pool resized

2015-02-12 14:14:00 +11:00

cifs

cifs: add missing Makefile

2014-12-16 10:48:51 +11:00

ext4

ext4/304: ignore EINVAL and ENODATA error

2015-02-12 14:13:44 +11:00

generic

generic: add test for fsync after creating hard link

2015-02-16 10:13:27 +11:00

shared

shared/032: handle mkfs.* in either /sbin or /usr/sbin

2015-02-12 14:11:04 +11:00

udf

xfstests: stop special casing nfs and udf

2013-12-03 10:29:26 +11:00

xfs

generic: relocate log recovery tests into tests/generic/

2015-02-12 14:22:59 +11:00

Makefile

xfstests: update method to set TESTS_SUBDIRS in tests/Makefile.

2013-05-13 15:41:21 -05:00