diff options
| author | David Sterba <dsterba@suse.com> | 2018-04-05 02:19:50 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2018-10-15 18:23:38 +0300 |
| commit | 9b142115ed3593480b813a9331593e9f199da340 (patch) | |
| tree | 1ba0e3ca09fa57e8a591aa7f8ef850415d1ce1f3 /fs | |
| parent | 7f8d236ae132a8886a0186008c828e21f7460474 (diff) | |
| download | linux-9b142115ed3593480b813a9331593e9f199da340.tar.xz | |
btrfs: dev-replace: remove pointless assert in write unlock
The value of blocking_readers is increased only when the lock is taken
for read, no way we can fail the condition with the write lock.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/btrfs/dev-replace.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c index d1ea76bccaaf..2aa48aecc52b 100644 --- a/fs/btrfs/dev-replace.c +++ b/fs/btrfs/dev-replace.c @@ -982,7 +982,6 @@ again: void btrfs_dev_replace_write_unlock(struct btrfs_dev_replace *dev_replace) { - ASSERT(atomic_read(&dev_replace->blocking_readers) == 0); write_unlock(&dev_replace->lock); } |