macos: avoid leaking iocount on synthetic fsevents

in certain cases we could leak an iocount. clean up even if
our event couldn't be run

Reviewed-on: http://gerrit.openafs.org/8777
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
Reviewed-by: Derrick Brashear <shadow@your-file-system.com>
(cherry picked from commit cf150252b6)

Change-Id: Id8c94bee3663507d31c0e0dc719693d82f90a151
Reviewed-on: http://gerrit.openafs.org/8791
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
Reviewed-by: Paul Smeddle <paul.smeddle@gmail.com>
This commit is contained in:
Derrick Brashear 2012-12-18 09:04:15 -05:00 committed by Paul Smeddle
parent f69aaf6914
commit bff5e77d97

View File

@ -88,6 +88,10 @@ loop:
vnode_put(vp);
AFS_GLOCK();
ReleaseWriteLock(&tvc->lock);
} else {
AFS_GUNLOCK();
vnode_put(vp);
AFS_GLOCK();
}
ObtainReadLock(&afs_xvcache);
uq = QPrev(tq);