Btrfs: use seqlock to protect fs_info->avail_{data, metadata, system}_alloc_bits

Browse source

There is no lock to protect
  fs_info->avail_{data, metadata, system}_alloc_bits,
it may introduce some problem, such as the wrong profile
information, so we add a seqlock to protect them.

Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Josef Bacik <jbacik@fusionio.com>

...

This commit is contained in:

Miao Xie 2013-01-29 10:13:12 +00:00 • committed by Josef Bacik

parent df0af1a57f

commit de98ced9e7

4 changed files with 49 additions and 32 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/ctree.h

View file

1

fs/btrfs/disk-io.c

View file

22

fs/btrfs/extent-tree.c

View file

56

fs/btrfs/volumes.c

View file