FBSD: Avoid requiring VI_FREE

FreeBSD commit cc3593fbd953e2eeec72dbca05e77632817cba0b (vfs: rework
vnode list management) removes VI_FREE. Our only user of VI_FREE is
some extra debug logging, so just pretend the flag isn't set if
VI_FREE isn't defined.

Change-Id: I77cc13683602bc1c1b920331847153371fbf4969
Reviewed-on: https://gerrit.openafs.org/15167
Reviewed-by: Michael Meffie <mmeffie@sinenomine.net>
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
This commit is contained in:
Andrew Deason 2022-10-25 14:57:28 -05:00
parent 68be40e469
commit 606d794b2b

View File

@ -624,11 +624,13 @@ afs_close(OSI_VC_DECL(avc), afs_int32 aflags, afs_ucred_t *acred)
#if defined(AFS_FBSD_ENV)
/* XXX */
if (!avc->opens) {
afs_int32 opens, is_free, is_gone, is_doomed, iflag;
afs_int32 opens, is_free = 0, is_gone, is_doomed, iflag;
struct vnode *vp = AFSTOV(avc);
VI_LOCK(vp);
is_doomed = AFS_IS_DOOMED(vp);
# ifdef VI_FREE
is_free = vp->v_iflag & VI_FREE;
# endif
is_gone = vp->v_iflag & VI_DOINGINACT;
iflag = vp->v_iflag;
VI_UNLOCK(vp);