Skip to content

Commit

Permalink
[GFS2] Remove incorrect initialisation of gh_owner
Browse files Browse the repository at this point in the history
The gh_owner field shouldn't be set or reset outside the glock code.
These were left over from when recursive locking was allowed. It
isn't any more, so they are not needed.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
  • Loading branch information
Steven Whitehouse committed May 12, 2006
1 parent e90c01e commit 9801f64
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 6 deletions.
1 change: 0 additions & 1 deletion fs/gfs2/inode.c
Original file line number Diff line number Diff line change
Expand Up @@ -319,7 +319,6 @@ static int inode_create(struct gfs2_glock *i_gl, const struct gfs2_inum *inum,
if (error)
goto fail;
}
ip->i_iopen_gh.gh_owner = NULL;

spin_lock(&io_gl->gl_spin);
gfs2_glock_hold(i_gl);
Expand Down
5 changes: 0 additions & 5 deletions fs/gfs2/ops_fstype.c
Original file line number Diff line number Diff line change
Expand Up @@ -468,11 +468,6 @@ static int init_journal(struct gfs2_sbd *sdp, int undo)
gfs2_glock_dq_uninit(&ji_gh);
jindex = 0;

/* Disown my Journal glock */

sdp->sd_journal_gh.gh_owner = NULL;
sdp->sd_jinode_gh.gh_owner = NULL;

p = kthread_run(gfs2_recoverd, sdp, "gfs2_recoverd");
error = IS_ERR(p);
if (error) {
Expand Down

0 comments on commit 9801f64

Please sign in to comment.