On Mon, Nov 12, 2018 at 10:24:30AM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> 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
On Mon, Nov 12, 2018 at 10:24:30AM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> 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
On 12.11.18 г. 12:24 ч., fdman...@kernel.org wrote:
> From: Filipe Manana
>
> 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
>
From: Filipe Manana
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
