btrfs: switch extent_buffer write_locks from atomic to int
authorDavid Sterba <dsterba@suse.com>
Thu, 2 May 2019 14:53:47 +0000 (16:53 +0200)
committerDavid Sterba <dsterba@suse.com>
Tue, 2 Jul 2019 10:30:47 +0000 (12:30 +0200)
commit00801ae4bb2be5f5af46502ef239ac5f4b536094
treed9835c3f4d44ecc3c4aa15c3707c4aea1a243ee3
parentf3dc24c52a28c700e35757dce7b38456888071e1
btrfs: switch extent_buffer write_locks from atomic to int

The write_locks is either 0 or 1 and always updated under the lock,
so we don't need the atomic_t semantics.

Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent_io.c
fs/btrfs/extent_io.h
fs/btrfs/locking.c
fs/btrfs/print-tree.c