btrfs: switch extent_buffer blocking_writers from atomic to int

Browse source

The blocking_writers 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>

...

This commit is contained in:

David Sterba 2019-05-02 16:47:23 +02:00

parent 38e9372e39

commit 06297d8cef

4 changed files with 23 additions and 29 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/btrfs/extent_io.c

View file

2

fs/btrfs/extent_io.h

View file

46

fs/btrfs/locking.c

View file

2

fs/btrfs/print-tree.c

View file