summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>1998-05-31 01:03:07 +0000
committerpeter <peter@FreeBSD.org>1998-05-31 01:03:07 +0000
commitc8c505e6c085ef10f4a357b2c99e9b9496cd3a63 (patch)
treef0da4b365cda829184bff2d6f2596b49cb731741
parentf31b4aebd75731bc784781a25ac5cd478a58e20c (diff)
downloadFreeBSD-src-c8c505e6c085ef10f4a357b2c99e9b9496cd3a63.zip
FreeBSD-src-c8c505e6c085ef10f4a357b2c99e9b9496cd3a63.tar.gz
VOP_ABORTUP() appears to be called with the wrong vnode. The other callers
that I checked (eg: ufs_link()) do the ABORTOP on the directory rather than the file itself. After Michael Hancock's patches, the abortop doesn't seem all that critial now since something else will free the pathname buffer.
-rw-r--r--sys/nfs/nfs_vnops.c4
-rw-r--r--sys/nfsclient/nfs_vnops.c4
2 files changed, 4 insertions, 4 deletions
diff --git a/sys/nfs/nfs_vnops.c b/sys/nfs/nfs_vnops.c
index dc8629d..853fd1b 100644
--- a/sys/nfs/nfs_vnops.c
+++ b/sys/nfs/nfs_vnops.c
@@ -34,7 +34,7 @@
* SUCH DAMAGE.
*
* @(#)nfs_vnops.c 8.16 (Berkeley) 5/27/95
- * $Id: nfs_vnops.c,v 1.89 1998/05/19 07:11:26 peter Exp $
+ * $Id: nfs_vnops.c,v 1.90 1998/05/30 16:33:57 peter Exp $
*/
@@ -1670,7 +1670,7 @@ nfs_link(ap)
int v3 = NFS_ISV3(vp);
if (vp->v_mount != tdvp->v_mount) {
- VOP_ABORTOP(vp, cnp);
+ VOP_ABORTOP(tdvp, cnp);
return (EXDEV);
}
diff --git a/sys/nfsclient/nfs_vnops.c b/sys/nfsclient/nfs_vnops.c
index dc8629d..853fd1b 100644
--- a/sys/nfsclient/nfs_vnops.c
+++ b/sys/nfsclient/nfs_vnops.c
@@ -34,7 +34,7 @@
* SUCH DAMAGE.
*
* @(#)nfs_vnops.c 8.16 (Berkeley) 5/27/95
- * $Id: nfs_vnops.c,v 1.89 1998/05/19 07:11:26 peter Exp $
+ * $Id: nfs_vnops.c,v 1.90 1998/05/30 16:33:57 peter Exp $
*/
@@ -1670,7 +1670,7 @@ nfs_link(ap)
int v3 = NFS_ISV3(vp);
if (vp->v_mount != tdvp->v_mount) {
- VOP_ABORTOP(vp, cnp);
+ VOP_ABORTOP(tdvp, cnp);
return (EXDEV);
}
OpenPOWER on IntegriCloud