btrfs: Fix no_space in write and rm loop
authorZhao Lei <zhaolei@cn.fujitsu.com>
Tue, 1 Dec 2015 10:39:40 +0000 (18:39 +0800)
committerSasha Levin <sasha.levin@oracle.com>
Wed, 13 Apr 2016 21:14:26 +0000 (17:14 -0400)
commitd5b55a7aae08c0e0785430126bcc4a9ae7f5c737
tree7dff05df6d81633d5d1106033ebc1576bb63f7b9
parent42bd8f4fda813558c3045c60ad6436b1c7430ec7
btrfs: Fix no_space in write and rm loop

[ Upstream commit 08acfd9dd845dc052c5eae33e6c3976338070069 ]

commit e1746e8381cd2af421f75557b5cae3604fc18b35 upstream.

I see no_space in v4.4-rc1 again in xfstests generic/102.
It happened randomly in some node only.
(one of 4 phy-node, and a kvm with non-virtio block driver)

By bisect, we can found the first-bad is:
 commit bdced438acd8 ("block: setup bi_phys_segments after splitting")'
But above patch only triggered the bug by making bio operation
faster(or slower).

Main reason is in our space_allocating code, we need to commit
page writeback before wait it complish, this patch fixed above
bug.

BTW, there is another reason for generic/102 fail, caused by
disable default mixed-blockgroup, I'll fix it in xfstests.

Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
Signed-off-by: Chris Mason <clm@fb.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
fs/btrfs/extent-tree.c