diff options
| author | bp <bp@FreeBSD.org> | 2001-05-18 07:43:13 +0000 |
|---|---|---|
| committer | bp <bp@FreeBSD.org> | 2001-05-18 07:43:13 +0000 |
| commit | 85b499e6f868ac8c73b82e03d9db2515e623c786 (patch) | |
| tree | 0a11009506aea7183cd85911a4a404c2f2c60d16 /sys | |
| parent | 0a6dd12de13b4e5f6c191716076be4c167ce646a (diff) | |
| download | FreeBSD-src-85b499e6f868ac8c73b82e03d9db2515e623c786.zip FreeBSD-src-85b499e6f868ac8c73b82e03d9db2515e623c786.tar.gz | |
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).
Diffstat (limited to 'sys')
| -rw-r--r-- | sys/fs/unionfs/union_vnops.c | 2 | ||||
| -rw-r--r-- | sys/miscfs/union/union_vnops.c | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/sys/fs/unionfs/union_vnops.c b/sys/fs/unionfs/union_vnops.c index 93922ec..3402825 100644 --- a/sys/fs/unionfs/union_vnops.c +++ b/sys/fs/unionfs/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)); } diff --git a/sys/miscfs/union/union_vnops.c b/sys/miscfs/union/union_vnops.c index 93922ec..3402825 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)); } |
