btrfs: make can_nocow_extent nowait compatible
If we have NOWAIT specified on our IOCB and we're writing into a PREALLOC or NOCOW extent then we need to be able to tell can_nocow_extent that we don't want to wait on any locks or metadata IO. Fix can_nocow_extent to allow for NOWAIT. Reviewed-by:Filipe Manana <fdmanana@suse.com> Signed-off-by:
Josef Bacik <josef@toxicpanda.com> Signed-off-by:
Stefan Roesch <shr@fb.com> Reviewed-by:
David Sterba <dsterba@suse.com> Signed-off-by:
David Sterba <dsterba@suse.com>
Showing
- fs/btrfs/ctree.h 3 additions, 2 deletionsfs/btrfs/ctree.h
- fs/btrfs/extent-tree.c 6 additions, 0 deletionsfs/btrfs/extent-tree.c
- fs/btrfs/file-item.c 3 additions, 1 deletionfs/btrfs/file-item.c
- fs/btrfs/file.c 1 addition, 1 deletionfs/btrfs/file.c
- fs/btrfs/inode.c 10 additions, 6 deletionsfs/btrfs/inode.c
- fs/btrfs/relocation.c 1 addition, 1 deletionfs/btrfs/relocation.c
- fs/btrfs/scrub.c 2 additions, 2 deletionsfs/btrfs/scrub.c
- fs/btrfs/tree-log.c 3 additions, 3 deletionsfs/btrfs/tree-log.c
Loading
Please register or sign in to comment