GFS2: Clean up reservation removal
authorSteven Whitehouse <swhiteho@redhat.com>
Fri, 27 Sep 2013 11:49:33 +0000 (12:49 +0100)
committerSteven Whitehouse <swhiteho@redhat.com>
Fri, 27 Sep 2013 11:49:33 +0000 (12:49 +0100)
commitaf5c269799feaef110e59ce55b497cdd08712b0c
treec5aad271b31ba67c5eef857b927ed2dc45186176
parent5ca1db41ecdeb0358b968265fadb755213558a85
GFS2: Clean up reservation removal

The reservation for an inode should be cleared when it is truncated so
that we can start again at a different offset for future allocations.
We could try and do better than that, by resetting the search based on
where the truncation started from, but this is only a first step.

In addition, there are three callers of gfs2_rs_delete() but only one
of those should really be testing the value of i_writecount. While
we get away with that in the other cases currently, I think it would
be better if we made that test specific to the one case which
requires it.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/gfs2/bmap.c
fs/gfs2/file.c
fs/gfs2/inode.c
fs/gfs2/rgrp.c
fs/gfs2/rgrp.h
fs/gfs2/super.c