Skip to content

Commit

Permalink
[XFS] allow a null behaviour pointer in linvfs_clear_inode
Browse files Browse the repository at this point in the history
SGI-PV: 940531
SGI-Modid: xfs-linux:xfs-kern:197782a

Signed-off-by: Christoph Hellwig <hch@sgi.com>
Signed-off-by: Nathan Scott <nathans@sgi.com>
  • Loading branch information
Christoph Hellwig authored and Nathan Scott committed Sep 4, 2005
1 parent 53937c5 commit 02ba71d
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions fs/xfs/linux-2.6/xfs_super.c
Original file line number Diff line number Diff line change
Expand Up @@ -387,14 +387,17 @@ linvfs_clear_inode(

vn_trace_entry(vp, "clear_inode", (inst_t *)__return_address);

ASSERT(vp->v_fbhv != NULL);

XFS_STATS_INC(vn_rele);
XFS_STATS_INC(vn_remove);
XFS_STATS_INC(vn_reclaim);
XFS_STATS_DEC(vn_active);

VOP_INACTIVE(vp, NULL, cache);
/*
* This can happen because xfs_iget_core calls xfs_idestroy if we
* find an inode with di_mode == 0 but without IGET_CREATE set.
*/
if (vp->v_fbhv)
VOP_INACTIVE(vp, NULL, cache);

VN_LOCK(vp);
vp->v_flag &= ~VMODIFIED;
Expand Down

0 comments on commit 02ba71d

Please sign in to comment.