Skip to content

Commit b870890

Browse files
AstralBobswhiteho
authored andcommitted
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>
1 parent 7e230f5 commit b870890

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

fs/gfs2/rgrp.c

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1825,7 +1825,6 @@ int gfs2_inplace_reserve(struct gfs2_inode *ip, u32 requested, u32 aflags)
18251825
return -EINVAL;
18261826
if (gfs2_rs_active(rs)) {
18271827
begin = rs->rs_rbm.rgd;
1828-
flags = 0; /* Yoda: Do or do not. There is no try */
18291828
} else if (ip->i_rgd && rgrp_contains_block(ip->i_rgd, ip->i_goal)) {
18301829
rs->rs_rbm.rgd = begin = ip->i_rgd;
18311830
} else {

0 commit comments

Comments
 (0)