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 cf150252b688dff0224f32be66d88347d1d94b37)

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>

diff --git a/src/afs/DARWIN/osi_misc.c b/src/afs/DARWIN/osi_misc.c
index b6d272671728800dc2c93f3c28a5552426fcc8ac..03c7abb8688aa6ee8c6b6872ba62f20de98fea7e 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);