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

Change-Id: I3a69f637c38478ac5f20a42af7db7f8a0ba7539a
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>

diff --git a/src/afs/DARWIN/osi_misc.c b/src/afs/DARWIN/osi_misc.c
index 03792d9..e0de037 100644 (file)
--- a/src/afs/DARWIN/osi_misc.c
+++ b/src/afs/DARWIN/osi_misc.c
@@ -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);