summaryrefslogtreecommitdiff
path: root/scripts/export_report.pl
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2018-05-11 16:42:42 +0100
committerDavid Sterba <dsterba@suse.com>2018-05-14 16:42:43 +0200
commit9a8fca62aacc1599fea8e813d01e1955513e4fad (patch)
treef33583926e5bdd53da4c77e035b3fe462403d6c3 /scripts/export_report.pl
parent6f2f0b394b54e2b159ef969a0b5274e9bbf82ff2 (diff)
Btrfs: fix xattr loss after power failure
If a file has xattrs, we fsync it, to ensure we clear the flags BTRFS_INODE_NEEDS_FULL_SYNC and BTRFS_INODE_COPY_EVERYTHING from its inode, the current transaction commits and then we fsync it (without either of those bits being set in its inode), we end up not logging all its xattrs. This results in deleting all xattrs when replying the log after a power failure. Trivial reproducer $ mkfs.btrfs -f /dev/sdb $ mount /dev/sdb /mnt $ touch /mnt/foobar $ setfattr -n user.xa -v qwerty /mnt/foobar $ xfs_io -c "fsync" /mnt/foobar $ sync $ xfs_io -c "pwrite -S 0xab 0 64K" /mnt/foobar $ xfs_io -c "fsync" /mnt/foobar <power failure> $ mount /dev/sdb /mnt $ getfattr --absolute-names --dump /mnt/foobar <empty output> $ So fix this by making sure all xattrs are logged if we log a file's inode item and neither the flags BTRFS_INODE_NEEDS_FULL_SYNC nor BTRFS_INODE_COPY_EVERYTHING were set in the inode. Fixes: 36283bf777d9 ("Btrfs: fix fsync xattr loss in the fast fsync path") Cc: <stable@vger.kernel.org> # 4.2+ Signed-off-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'scripts/export_report.pl')
0 files changed, 0 insertions, 0 deletions