kernel.git/fs/btrfs/tree-log.h, branch linux-5.5.y

btrfs: get fs_info from trans in btrfs_set_log_full_commit

2019-04-29T17:02:41Z

We can read fs_info from the transaction and can drop it from the parameters. Signed-off-by: David Sterba

btrfs: get fs_info from trans in btrfs_need_log_full_commit

2019-04-29T17:02:41Z

We can read fs_info from the transaction and can drop it from the parameters. Signed-off-by: David Sterba

Btrfs: remove no longer used io_err from btrfs_log_ctx

2018-12-17T13:51:31Z

The io_err field of struct btrfs_log_ctx is no longer used after the recent simplification of the fast fsync path, where we now wait for ordered extents to complete before logging the inode. We did this in commit b5e6c3e170b7 ("btrfs: always wait on ordered extents at fsync time") and commit a2120a473a80 ("btrfs: clean up the left over logged_list usage") removed its last use. Reviewed-by: Nikolay Borisov Reviewed-by: Josef Bacik Signed-off-by: Filipe Manana Signed-off-by: David Sterba

btrfs: change btrfs_pin_log_trans to return void

2018-10-15T15:23:27Z

btrfs_pin_log_trans defines the variable "ret" for return value, but it is not modified after initialization. Further, I find that none of the callers do handles the return value, so it is safe to drop the unneeded "ret" and make it return void. Signed-off-by: zhong jiang Reviewed-by: David Sterba Signed-off-by: David Sterba

Btrfs: sync log after logging new name

2018-08-23T15:37:26Z

When we add a new name for an inode which was logged in the current transaction, we update the inode in the log so that its new name and ancestors are added to the log. However when we do this we do not persist the log, so the changes remain in memory only, and as a consequence, any ancestors that were created in the current transaction are updated such that future calls to btrfs_inode_in_log() return true. This leads to a subsequent fsync against such new ancestor directories returning immediately, without persisting the log, therefore after a power failure the new ancestor directories do not exist, despite fsync being called against them explicitly. Example: $ mkfs.btrfs -f /dev/sdb $ mount /dev/sdb /mnt $ mkdir /mnt/A $ mkdir /mnt/B $ mkdir /mnt/A/C $ touch /mnt/B/foo $ xfs_io -c "fsync" /mnt/B/foo $ ln /mnt/B/foo /mnt/A/C/foo $ xfs_io -c "fsync" /mnt/A After the power failure, directory "A" does not exist, despite the explicit fsync on it. Instead of fixing this by changing the behaviour of the explicit fsync on directory "A" to persist the log instead of doing nothing, make the logging of the new file name (which happens when creating a hard link or renaming) persist the log. This approach not only is simpler, not requiring addition of new fields to the inode in memory structure, but also gives us the same behaviour as ext4, xfs and f2fs (possibly other filesystems too). A test case for fstests follows soon. Fixes: 12fcfd22fe5b ("Btrfs: tree logging unlink/rename fixes") Reported-by: Vijay Chidambaram Signed-off-by: Filipe Manana Signed-off-by: David Sterba

btrfs: replace GPL boilerplate by SPDX -- headers

2018-04-12T14:29:46Z

Remove GPL boilerplate text (long, short, one-line) and keep the rest, ie. personal, company or original source copyright statements. Add the SPDX header. Unify the include protection macros to match the file names. Signed-off-by: David Sterba

btrfs: Remove root argument from btrfs_log_dentry_safe

2018-03-26T13:09:42Z

Now that nothing uses the root arg of btrfs_log_dentry_safe it can be safely removed. No functional changes. Signed-off-by: Nikolay Borisov Signed-off-by: David Sterba

btrfs: Make btrfs_del_inode_ref take btrfs_inode

2017-02-14T14:50:54Z

Signed-off-by: Nikolay Borisov Signed-off-by: David Sterba

btrfs: Make btrfs_del_dir_entries_in_log take btrfs_inode

2017-02-14T14:50:54Z

Signed-off-by: Nikolay Borisov Signed-off-by: David Sterba

btrfs: Make btrfs_log_new_name take btrfs_inode

2017-02-14T14:50:54Z

Signed-off-by: Nikolay Borisov Signed-off-by: David Sterba