Btrfs: introduce btrfs_{start, end}_nocow_write() for each subvolume

Browse source

If the snapshot creation happened after the nocow write but before the dirty
data flush, we would fail to flush the dirty data because of no space.

So we must keep track of when those nocow write operations start and when they
end, if there are nocow writers, the snapshot creators must wait. In order
to implement this function, I introduce btrfs_{start, end}_nocow_write(),
which is similar to mnt_{want,drop}_write().

These two functions are only used for nocow file write operations.

Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Josef Bacik <jbacik@fb.com>

...

This commit is contained in:

Miao Xie 2014-03-06 13:38:19 +08:00 • committed by Josef Bacik

parent 52483bc26f

commit 8257b2dc3c

5 changed files with 133 additions and 10 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

10

fs/btrfs/ctree.h

View file

42

fs/btrfs/disk-io.c

View file

35

fs/btrfs/extent-tree.c

View file

21

fs/btrfs/file.c

View file

35

fs/btrfs/ioctl.c

View file