aboutsummaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_dquot.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@infradead.org>2012-02-19 21:31:22 -0500
committerBen Myers <bpm@sgi.com>2012-02-22 23:17:00 -0500
commit5b03ff1b2444ddf7b8084b7505101e97257aff5a (patch)
tree25f783fa62973601e40d6af29ccf44a51b35267a /fs/xfs/xfs_dquot.c
parent3af1de753b3caf9fa3762b4b1b85d833c121847e (diff)
xfs: remove xfs_trans_unlocked_item
There is no reason to wake up log space waiters when unlocking inodes or dquots, and the commit log has no explanation for this function either. Given that we now have exact log space wakeups everywhere we can assume the reason for this function was to paper over log space races in earlier XFS versions. Reviewed-by: Mark Tinguely <tinguely@sgi.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/xfs/xfs_dquot.c')
-rw-r--r--fs/xfs/xfs_dquot.c11
1 files changed, 0 insertions, 11 deletions
diff --git a/fs/xfs/xfs_dquot.c b/fs/xfs/xfs_dquot.c
index 4e268edcf3f6..71e615fef174 100644
--- a/fs/xfs/xfs_dquot.c
+++ b/fs/xfs/xfs_dquot.c
@@ -1076,17 +1076,6 @@ xfs_qm_dqflush(
1076 1076
1077} 1077}
1078 1078
1079void
1080xfs_dqunlock(
1081 xfs_dquot_t *dqp)
1082{
1083 xfs_dqunlock_nonotify(dqp);
1084 if (dqp->q_logitem.qli_dquot == dqp) {
1085 xfs_trans_unlocked_item(dqp->q_logitem.qli_item.li_ailp,
1086 &dqp->q_logitem.qli_item);
1087 }
1088}
1089
1090/* 1079/*
1091 * Lock two xfs_dquot structures. 1080 * Lock two xfs_dquot structures.
1092 * 1081 *