GFS2: Do not reset flags on active reservations
When we used try locks for rgrps on block allocations, it was important to clear the flags field so that we used a blocking hold on the glock. Now that we're not doing try locks, clearing flags is unnecessary, and a waste of time. In fact, it's probably doing the wrong thing because it clears the GL_SKIP bit that was set for the lvb tracking purposes. Signed-off-by: Bob Peterson <rpeterso@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
This commit is contained in:
parent
7e230f5774
commit
b870890519
|
@ -1825,7 +1825,6 @@ int gfs2_inplace_reserve(struct gfs2_inode *ip, u32 requested, u32 aflags)
|
||||||
return -EINVAL;
|
return -EINVAL;
|
||||||
if (gfs2_rs_active(rs)) {
|
if (gfs2_rs_active(rs)) {
|
||||||
begin = rs->rs_rbm.rgd;
|
begin = rs->rs_rbm.rgd;
|
||||||
flags = 0; /* Yoda: Do or do not. There is no try */
|
|
||||||
} else if (ip->i_rgd && rgrp_contains_block(ip->i_rgd, ip->i_goal)) {
|
} else if (ip->i_rgd && rgrp_contains_block(ip->i_rgd, ip->i_goal)) {
|
||||||
rs->rs_rbm.rgd = begin = ip->i_rgd;
|
rs->rs_rbm.rgd = begin = ip->i_rgd;
|
||||||
} else {
|
} else {
|
||||||
|
|
Loading…
Reference in New Issue