xfs: perag initialization should only touch m_ag_max_usable for AG 0
authorDarrick J. Wong <darrick.wong@oracle.com>
Mon, 18 Sep 2017 16:42:09 +0000 (09:42 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 27 Oct 2017 08:38:09 +0000 (10:38 +0200)
commit98cbca24894c592499bf135d3f3f5bd9f8f6946d
tree2ce031ecdb52eda64e0afa6448e40662b96295c4
parent0eebfedec1449f31c2321723acdd3c36dcac7f0a
xfs: perag initialization should only touch m_ag_max_usable for AG 0

commit 9789dd9e1d939232e8ff4c50ef8e75aa6781b3fb upstream.

We call __xfs_ag_resv_init to make a per-AG reservation for each AG.
This makes the reservation per-AG, not per-filesystem.  Therefore, it
is incorrect to adjust m_ag_max_usable for each AG.  Adjust it only
when we're reserving AG 0's blocks so that we only do it once per fs.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/xfs/libxfs/xfs_ag_resv.c