aboutsummaryrefslogtreecommitdiff
path: root/sys/miscfs
diff options
context:
space:
mode:
authorBoris Popov <bp@FreeBSD.org>2001-05-18 07:43:13 +0000
committerBoris Popov <bp@FreeBSD.org>2001-05-18 07:43:13 +0000
commit10fa1684ed3be7246e2704dfa94e1dd53f306d45 (patch)
tree38a68f4ce61bf1cbb02e394de19e7cd1676dd0f4 /sys/miscfs
parent108b08b24e330a534b219378d68db1ee6467f366 (diff)
Currently there is no way to tell if write operation invoked via
vn_start_write() on the given vnode will be successful. VOP_LEASE() may help to solve this problem, but its return value ignored nearly everywhere. For now just assume that the missing upper layer on write means insufficient access rights (which is correct for most cases).
Notes
Notes: svn path=/head/; revision=76797
Diffstat (limited to 'sys/miscfs')
-rw-r--r--sys/miscfs/union/union_vnops.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/miscfs/union/union_vnops.c b/sys/miscfs/union/union_vnops.c
index 93922ecabaaa..3402825820f6 100644
--- a/sys/miscfs/union/union_vnops.c
+++ b/sys/miscfs/union/union_vnops.c
@@ -1630,7 +1630,7 @@ union_getwritemount(ap)
return (EOPNOTSUPP);
}
VI_UNLOCK(vp);
- panic("union_getwritemount: missing upper layer");
+ return (EACCES);
}
return(VOP_GETWRITEMOUNT(uvp, ap->a_mpp));
}