From ad8e2a2c53409ba5af5c25f511693706568c5fef Mon Sep 17 00:00:00 2001 From: dfr Date: Thu, 4 Jun 2009 08:13:51 +0000 Subject: Don't panic in nlm_record_lock if we get ENOENT from lf_advlockasync. This is likely to be because the file was just removed and in our context this is harmless. --- sys/nlm/nlm_advlock.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'sys/nlm/nlm_advlock.c') diff --git a/sys/nlm/nlm_advlock.c b/sys/nlm/nlm_advlock.c index 0be799d..2d94045 100644 --- a/sys/nlm/nlm_advlock.c +++ b/sys/nlm/nlm_advlock.c @@ -716,8 +716,8 @@ nlm_record_lock(struct vnode *vp, int op, struct flock *fl, newfl.l_sysid = NLM_SYSID_CLIENT | sysid; error = lf_advlockasync(&a, &vp->v_lockf, size); - KASSERT(error == 0, ("Failed to register NFS lock locally - error=%d", - error)); + KASSERT(error == 0 || errno == ENOENT, + ("Failed to register NFS lock locally - error=%d", error)); } static int -- cgit v1.1