1 /* $NetBSD: layer_vnops.c,v 1.3 2000/03/30 12:22:14 augustss Exp $ */ 2 3 /* 4 * Copyright (c) 1999 National Aeronautics & Space Administration 5 * All rights reserved. 6 * 7 * This software was written by William Studenmund of the 8 * Numerical Aerospace Similation Facility, NASA Ames Research Center. 9 * 10 * Redistribution and use in source and binary forms, with or without 11 * modification, are permitted provided that the following conditions 12 * are met: 13 * 1. Redistributions of source code must retain the above copyright 14 * notice, this list of conditions and the following disclaimer. 15 * 2. Redistributions in binary form must reproduce the above copyright 16 * notice, this list of conditions and the following disclaimer in the 17 * documentation and/or other materials provided with the distribution. 18 * 3. Neither the name of the National Aeronautics & Space Administration 19 * nor the names of its contributors may be used to endorse or promote 20 * products derived from this software without specific prior written 21 * permission. 22 * 23 * THIS SOFTWARE IS PROVIDED BY THE NATIONAL AERONAUTICS & SPACE ADMINISTRATION 24 * ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 25 * TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 26 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ADMINISTRATION OR CONTRIB- 27 * UTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, 28 * OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 29 * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 30 * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 31 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 32 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 33 * POSSIBILITY OF SUCH DAMAGE. 34 */ 35 /* 36 * Copyright (c) 1992, 1993 37 * The Regents of the University of California. All rights reserved. 38 * 39 * This code is derived from software contributed to Berkeley by 40 * John Heidemann of the UCLA Ficus project. 41 * 42 * Redistribution and use in source and binary forms, with or without 43 * modification, are permitted provided that the following conditions 44 * are met: 45 * 1. Redistributions of source code must retain the above copyright 46 * notice, this list of conditions and the following disclaimer. 47 * 2. Redistributions in binary form must reproduce the above copyright 48 * notice, this list of conditions and the following disclaimer in the 49 * documentation and/or other materials provided with the distribution. 50 * 3. All advertising materials mentioning features or use of this software 51 * must display the following acknowledgement: 52 * This product includes software developed by the University of 53 * California, Berkeley and its contributors. 54 * 4. Neither the name of the University nor the names of its contributors 55 * may be used to endorse or promote products derived from this software 56 * without specific prior written permission. 57 * 58 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 59 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 60 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 61 * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 62 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 63 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 64 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 65 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 66 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 67 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 68 * SUCH DAMAGE. 69 * 70 * @(#)null_vnops.c 8.6 (Berkeley) 5/27/95 71 * 72 * Ancestors: 73 * @(#)lofs_vnops.c 1.2 (Berkeley) 6/18/92 74 * $Id: layer_vnops.c,v 1.3 2000/03/30 12:22:14 augustss Exp $ 75 * ...and... 76 * @(#)null_vnodeops.c 1.20 92/07/07 UCLA Ficus project 77 */ 78 79 /* 80 * Null Layer vnode routines. 81 * 82 * (See mount_null(8) for more information.) 83 * 84 * The layer.h, layer_extern.h, layer_vfs.c, and layer_vnops.c files provide 85 * the core implimentation of the null file system and most other stacked 86 * fs's. The description below refers to the null file system, but the 87 * services provided by the layer* files are useful for all layered fs's. 88 * 89 * The null layer duplicates a portion of the file system 90 * name space under a new name. In this respect, it is 91 * similar to the loopback file system. It differs from 92 * the loopback fs in two respects: it is implemented using 93 * a stackable layers techniques, and it's "null-node"s stack above 94 * all lower-layer vnodes, not just over directory vnodes. 95 * 96 * The null layer has two purposes. First, it serves as a demonstration 97 * of layering by proving a layer which does nothing. (It actually 98 * does everything the loopback file system does, which is slightly 99 * more than nothing.) Second, the null layer can serve as a prototype 100 * layer. Since it provides all necessary layer framework, 101 * new file system layers can be created very easily be starting 102 * with a null layer. 103 * 104 * The remainder of the man page examines the null layer as a basis 105 * for constructing new layers. 106 * 107 * 108 * INSTANTIATING NEW NULL LAYERS 109 * 110 * New null layers are created with mount_null(8). 111 * Mount_null(8) takes two arguments, the pathname 112 * of the lower vfs (target-pn) and the pathname where the null 113 * layer will appear in the namespace (alias-pn). After 114 * the null layer is put into place, the contents 115 * of target-pn subtree will be aliased under alias-pn. 116 * 117 * It is conceivable that other overlay filesystems will take different 118 * parameters. For instance, data migration or access controll layers might 119 * only take one pathname which will serve both as the target-pn and 120 * alias-pn described above. 121 * 122 * 123 * OPERATION OF A NULL LAYER 124 * 125 * The null layer is the minimum file system layer, 126 * simply bypassing all possible operations to the lower layer 127 * for processing there. The majority of its activity centers 128 * on the bypass routine, though which nearly all vnode operations 129 * pass. 130 * 131 * The bypass routine accepts arbitrary vnode operations for 132 * handling by the lower layer. It begins by examing vnode 133 * operation arguments and replacing any layered nodes by their 134 * lower-layer equivlants. It then invokes the operation 135 * on the lower layer. Finally, it replaces the layered nodes 136 * in the arguments and, if a vnode is return by the operation, 137 * stacks a layered node on top of the returned vnode. 138 * 139 * The bypass routine in this file, layer_bypass(), is suitable for use 140 * by many different layered filesystems. It can be used by multiple 141 * filesystems simultaneously. Alternatively, a layered fs may provide 142 * its own bypass routine, in which case layer_bypass() should be used as 143 * a model. For instance, the main functionality provided by umapfs, the user 144 * identity mapping file system, is handled by a custom bypass routine. 145 * 146 * Typically a layered fs registers its selected bypass routine as the 147 * default vnode operation in its vnodeopv_entry_desc table. Additionally 148 * the filesystem must store the bypass entry point in the layerm_bypass 149 * field of struct layer_mount. All other layer routines in this file will 150 * use the layerm_bypass routine. 151 * 152 * Although the bypass routine handles most operations outright, a number 153 * of operations are special cased, and handled by the layered fs. One 154 * group, layer_setattr, layer_getattr, layer_access, layer_open, and 155 * layer_fsync, perform layer-specific manipulation in addition to calling 156 * the bypass routine. The other group 157 158 * Although bypass handles most operations, vop_getattr, vop_lock, 159 * vop_unlock, vop_inactive, vop_reclaim, and vop_print are not 160 * bypassed. Vop_getattr must change the fsid being returned. 161 * Vop_lock and vop_unlock must handle any locking for the 162 * current vnode as well as pass the lock request down. 163 * Vop_inactive and vop_reclaim are not bypassed so that 164 * they can handle freeing null-layer specific data. Vop_print 165 * is not bypassed to avoid excessive debugging information. 166 * Also, certain vnode operations change the locking state within 167 * the operation (create, mknod, remove, link, rename, mkdir, rmdir, 168 * and symlink). Ideally these operations should not change the 169 * lock state, but should be changed to let the caller of the 170 * function unlock them. Otherwise all intermediate vnode layers 171 * (such as union, umapfs, etc) must catch these functions to do 172 * the necessary locking at their layer. 173 * 174 * 175 * INSTANTIATING VNODE STACKS 176 * 177 * Mounting associates the null layer with a lower layer, 178 * effect stacking two VFSes. Vnode stacks are instead 179 * created on demand as files are accessed. 180 * 181 * The initial mount creates a single vnode stack for the 182 * root of the new null layer. All other vnode stacks 183 * are created as a result of vnode operations on 184 * this or other null vnode stacks. 185 * 186 * New vnode stacks come into existance as a result of 187 * an operation which returns a vnode. 188 * The bypass routine stacks a null-node above the new 189 * vnode before returning it to the caller. 190 * 191 * For example, imagine mounting a null layer with 192 * "mount_null /usr/include /dev/layer/null". 193 * Changing directory to /dev/layer/null will assign 194 * the root null-node (which was created when the null layer was mounted). 195 * Now consider opening "sys". A vop_lookup would be 196 * done on the root null-node. This operation would bypass through 197 * to the lower layer which would return a vnode representing 198 * the UFS "sys". layer_bypass then builds a null-node 199 * aliasing the UFS "sys" and returns this to the caller. 200 * Later operations on the null-node "sys" will repeat this 201 * process when constructing other vnode stacks. 202 * 203 * 204 * CREATING OTHER FILE SYSTEM LAYERS 205 * 206 * One of the easiest ways to construct new file system layers is to make 207 * a copy of the null layer, rename all files and variables, and 208 * then begin modifing the copy. Sed can be used to easily rename 209 * all variables. 210 * 211 * The umap layer is an example of a layer descended from the 212 * null layer. 213 * 214 * 215 * INVOKING OPERATIONS ON LOWER LAYERS 216 * 217 * There are two techniques to invoke operations on a lower layer 218 * when the operation cannot be completely bypassed. Each method 219 * is appropriate in different situations. In both cases, 220 * it is the responsibility of the aliasing layer to make 221 * the operation arguments "correct" for the lower layer 222 * by mapping an vnode arguments to the lower layer. 223 * 224 * The first approach is to call the aliasing layer's bypass routine. 225 * This method is most suitable when you wish to invoke the operation 226 * currently being hanldled on the lower layer. It has the advantage 227 * that the bypass routine already must do argument mapping. 228 * An example of this is null_getattrs in the null layer. 229 * 230 * A second approach is to directly invoked vnode operations on 231 * the lower layer with the VOP_OPERATIONNAME interface. 232 * The advantage of this method is that it is easy to invoke 233 * arbitrary operations on the lower layer. The disadvantage 234 * is that vnodes arguments must be manualy mapped. 235 * 236 */ 237 238 #include <sys/param.h> 239 #include <sys/systm.h> 240 #include <sys/proc.h> 241 #include <sys/time.h> 242 #include <sys/types.h> 243 #include <sys/vnode.h> 244 #include <sys/mount.h> 245 #include <sys/namei.h> 246 #include <sys/malloc.h> 247 #include <sys/buf.h> 248 #include <miscfs/genfs/layer.h> 249 #include <miscfs/genfs/layer_extern.h> 250 #include <miscfs/genfs/genfs.h> 251 252 253 /* 254 * This is the 08-June-99 bypass routine, based on the 10-Apr-92 bypass 255 * routine by John Heidemann. 256 * The new element for this version is that the whole nullfs 257 * system gained the concept of locks on the lower node, and locks on 258 * our nodes. When returning from a call to the lower layer, we may 259 * need to update lock state ONLY on our layer. The LAYERFS_UPPER*LOCK() 260 * macros provide this functionality. 261 * The 10-Apr-92 version was optimized for speed, throwing away some 262 * safety checks. It should still always work, but it's not as 263 * robust to programmer errors. 264 * Define SAFETY to include some error checking code. 265 * 266 * In general, we map all vnodes going down and unmap them on the way back. 267 * 268 * Also, some BSD vnode operations have the side effect of vrele'ing 269 * their arguments. With stacking, the reference counts are held 270 * by the upper node, not the lower one, so we must handle these 271 * side-effects here. This is not of concern in Sun-derived systems 272 * since there are no such side-effects. 273 * 274 * New for the 08-June-99 version: we also handle operations which unlock 275 * the passed-in node (typically they vput the node). 276 * 277 * This makes the following assumptions: 278 * - only one returned vpp 279 * - no INOUT vpp's (Sun's vop_open has one of these) 280 * - the vnode operation vector of the first vnode should be used 281 * to determine what implementation of the op should be invoked 282 * - all mapped vnodes are of our vnode-type (NEEDSWORK: 283 * problems on rmdir'ing mount points and renaming?) 284 */ 285 int 286 layer_bypass(v) 287 void *v; 288 { 289 struct vop_generic_args /* { 290 struct vnodeop_desc *a_desc; 291 <other random data follows, presumably> 292 } */ *ap = v; 293 int (**our_vnodeop_p) __P((void *)); 294 struct vnode **this_vp_p; 295 int error, error1; 296 struct vnode *old_vps[VDESC_MAX_VPS], *vp0; 297 struct vnode **vps_p[VDESC_MAX_VPS]; 298 struct vnode ***vppp; 299 struct vnodeop_desc *descp = ap->a_desc; 300 int reles, i, flags; 301 302 #ifdef SAFETY 303 /* 304 * We require at least one vp. 305 */ 306 if (descp->vdesc_vp_offsets == NULL || 307 descp->vdesc_vp_offsets[0] == VDESC_NO_OFFSET) 308 panic ("layer_bypass: no vp's in map.\n"); 309 #endif 310 311 vps_p[0] = VOPARG_OFFSETTO(struct vnode**,descp->vdesc_vp_offsets[0],ap); 312 vp0 = *vps_p[0]; 313 flags = MOUNTTOLAYERMOUNT(vp0->v_mount)->layerm_flags; 314 our_vnodeop_p = vp0->v_op; 315 316 if (flags & LAYERFS_MBYPASSDEBUG) 317 printf ("layer_bypass: %s\n", descp->vdesc_name); 318 319 /* 320 * Map the vnodes going in. 321 * Later, we'll invoke the operation based on 322 * the first mapped vnode's operation vector. 323 */ 324 reles = descp->vdesc_flags; 325 for (i = 0; i < VDESC_MAX_VPS; reles >>= 1, i++) { 326 if (descp->vdesc_vp_offsets[i] == VDESC_NO_OFFSET) 327 break; /* bail out at end of list */ 328 vps_p[i] = this_vp_p = 329 VOPARG_OFFSETTO(struct vnode**,descp->vdesc_vp_offsets[i],ap); 330 /* 331 * We're not guaranteed that any but the first vnode 332 * are of our type. Check for and don't map any 333 * that aren't. (We must always map first vp or vclean fails.) 334 */ 335 if (i && (*this_vp_p == NULL || 336 (*this_vp_p)->v_op != our_vnodeop_p)) { 337 old_vps[i] = NULL; 338 } else { 339 old_vps[i] = *this_vp_p; 340 *(vps_p[i]) = LAYERVPTOLOWERVP(*this_vp_p); 341 /* 342 * XXX - Several operations have the side effect 343 * of vrele'ing their vp's. We must account for 344 * that. (This should go away in the future.) 345 */ 346 if (reles & VDESC_VP0_WILLRELE) 347 VREF(*this_vp_p); 348 } 349 350 } 351 352 /* 353 * Call the operation on the lower layer 354 * with the modified argument structure. 355 */ 356 error = VCALL(*vps_p[0], descp->vdesc_offset, ap); 357 358 /* 359 * Maintain the illusion of call-by-value 360 * by restoring vnodes in the argument structure 361 * to their original value. 362 */ 363 reles = descp->vdesc_flags; 364 for (i = 0; i < VDESC_MAX_VPS; reles >>= 1, i++) { 365 if (descp->vdesc_vp_offsets[i] == VDESC_NO_OFFSET) 366 break; /* bail out at end of list */ 367 if (old_vps[i]) { 368 *(vps_p[i]) = old_vps[i]; 369 if (reles & VDESC_VP0_WILLUNLOCK) 370 LAYERFS_UPPERUNLOCK(*(vps_p[i]), 0, error1); 371 if (reles & VDESC_VP0_WILLRELE) 372 vrele(*(vps_p[i])); 373 } 374 } 375 376 /* 377 * Map the possible out-going vpp 378 * (Assumes that the lower layer always returns 379 * a VREF'ed vpp unless it gets an error.) 380 */ 381 if (descp->vdesc_vpp_offset != VDESC_NO_OFFSET && 382 !(descp->vdesc_flags & VDESC_NOMAP_VPP) && 383 !error) { 384 /* 385 * XXX - even though some ops have vpp returned vp's, 386 * several ops actually vrele this before returning. 387 * We must avoid these ops. 388 * (This should go away when these ops are regularized.) 389 */ 390 if (descp->vdesc_flags & VDESC_VPP_WILLRELE) 391 goto out; 392 vppp = VOPARG_OFFSETTO(struct vnode***, 393 descp->vdesc_vpp_offset,ap); 394 /* 395 * Only vop_lookup, vop_create, vop_makedir, vop_bmap, 396 * vop_mknod, and vop_symlink return vpp's. The latter 397 * two are VPP_WILLRELE, so we won't get here, and vop_bmap 398 * doesn't call bypass as the lower vpp is fine (we're just 399 * going to do i/o on it). vop_loookup doesn't call bypass 400 * as a lookup on "." would generate a locking error. 401 * So all the calls which get us here have a locked vpp. :-) 402 */ 403 error = layer_node_create(old_vps[0]->v_mount, **vppp, *vppp); 404 } 405 406 out: 407 return (error); 408 } 409 410 /* 411 * We have to carry on the locking protocol on the layer vnodes 412 * as we progress through the tree. We also have to enforce read-only 413 * if this layer is mounted read-only. 414 */ 415 int 416 layer_lookup(v) 417 void *v; 418 { 419 struct vop_lookup_args /* { 420 struct vnodeop_desc *a_desc; 421 struct vnode * a_dvp; 422 struct vnode ** a_vpp; 423 struct componentname * a_cnp; 424 } */ *ap = v; 425 struct componentname *cnp = ap->a_cnp; 426 int flags = cnp->cn_flags; 427 struct vnode *dvp, *vp, *ldvp; 428 int error, r; 429 430 dvp = ap->a_dvp; 431 432 if ((flags & ISLASTCN) && (dvp->v_mount->mnt_flag & MNT_RDONLY) && 433 (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME)) 434 return (EROFS); 435 436 ldvp = LAYERVPTOLOWERVP(dvp); 437 ap->a_dvp = ldvp; 438 error = VCALL(ldvp, ap->a_desc->vdesc_offset, ap); 439 vp = *ap->a_vpp; 440 441 if (error == EJUSTRETURN && (flags & ISLASTCN) && 442 (dvp->v_mount->mnt_flag & MNT_RDONLY) && 443 (cnp->cn_nameiop == CREATE || cnp->cn_nameiop == RENAME)) 444 error = EROFS; 445 /* 446 * We must do the same locking and unlocking at this layer as 447 * is done in the layers below us. It used to be we would try 448 * to guess based on what was set with the flags and error codes. 449 * 450 * But that doesn't work. So now we have the underlying VOP_LOOKUP 451 * tell us if it released the parent vnode, and we adjust the 452 * upper node accordingly. We can't just look at the lock states 453 * of the lower nodes as someone else might have come along and 454 * locked the parent node after our call to VOP_LOOKUP locked it. 455 */ 456 if ((cnp->cn_flags & PDIRUNLOCK)) { 457 LAYERFS_UPPERUNLOCK(dvp, 0, r); 458 } 459 if (ldvp == vp) { 460 /* 461 * Did lookup on "." or ".." in the root node of a mount point. 462 * So we return dvp after a VREF. 463 */ 464 *ap->a_vpp = dvp; 465 VREF(dvp); 466 vrele(vp); 467 } else if (vp != NULL) { 468 error = layer_node_create(dvp->v_mount, vp, ap->a_vpp); 469 } 470 return (error); 471 } 472 473 /* 474 * Setattr call. Disallow write attempts if the layer is mounted read-only. 475 */ 476 int 477 layer_setattr(v) 478 void *v; 479 { 480 struct vop_setattr_args /* { 481 struct vnodeop_desc *a_desc; 482 struct vnode *a_vp; 483 struct vattr *a_vap; 484 struct ucred *a_cred; 485 struct proc *a_p; 486 } */ *ap = v; 487 struct vnode *vp = ap->a_vp; 488 struct vattr *vap = ap->a_vap; 489 490 if ((vap->va_flags != VNOVAL || vap->va_uid != (uid_t)VNOVAL || 491 vap->va_gid != (gid_t)VNOVAL || vap->va_atime.tv_sec != VNOVAL || 492 vap->va_mtime.tv_sec != VNOVAL || vap->va_mode != (mode_t)VNOVAL) && 493 (vp->v_mount->mnt_flag & MNT_RDONLY)) 494 return (EROFS); 495 if (vap->va_size != VNOVAL) { 496 switch (vp->v_type) { 497 case VDIR: 498 return (EISDIR); 499 case VCHR: 500 case VBLK: 501 case VSOCK: 502 case VFIFO: 503 return (0); 504 case VREG: 505 case VLNK: 506 default: 507 /* 508 * Disallow write attempts if the filesystem is 509 * mounted read-only. 510 */ 511 if (vp->v_mount->mnt_flag & MNT_RDONLY) 512 return (EROFS); 513 } 514 } 515 return (LAYERFS_DO_BYPASS(vp, ap)); 516 } 517 518 /* 519 * We handle getattr only to change the fsid. 520 */ 521 int 522 layer_getattr(v) 523 void *v; 524 { 525 struct vop_getattr_args /* { 526 struct vnode *a_vp; 527 struct vattr *a_vap; 528 struct ucred *a_cred; 529 struct proc *a_p; 530 } */ *ap = v; 531 struct vnode *vp = ap->a_vp; 532 int error; 533 534 if ((error = LAYERFS_DO_BYPASS(vp, ap)) != 0) 535 return (error); 536 /* Requires that arguments be restored. */ 537 ap->a_vap->va_fsid = vp->v_mount->mnt_stat.f_fsid.val[0]; 538 return (0); 539 } 540 541 int 542 layer_access(v) 543 void *v; 544 { 545 struct vop_access_args /* { 546 struct vnode *a_vp; 547 int a_mode; 548 struct ucred *a_cred; 549 struct proc *a_p; 550 } */ *ap = v; 551 struct vnode *vp = ap->a_vp; 552 mode_t mode = ap->a_mode; 553 554 /* 555 * Disallow write attempts on read-only layers; 556 * unless the file is a socket, fifo, or a block or 557 * character device resident on the file system. 558 */ 559 if (mode & VWRITE) { 560 switch (vp->v_type) { 561 case VDIR: 562 case VLNK: 563 case VREG: 564 if (vp->v_mount->mnt_flag & MNT_RDONLY) 565 return (EROFS); 566 break; 567 default: 568 break; 569 } 570 } 571 return (LAYERFS_DO_BYPASS(vp, ap)); 572 } 573 574 /* 575 * We must handle open to be able to catch MNT_NODEV and friends. 576 */ 577 int 578 layer_open(v) 579 void *v; 580 { 581 struct vop_open_args *ap = v; 582 struct vnode *vp = ap->a_vp; 583 enum vtype lower_type = LAYERVPTOLOWERVP(vp)->v_type; 584 585 if (((lower_type == VBLK) || (lower_type == VCHR)) && 586 (vp->v_mount->mnt_flag & MNT_NODEV)) 587 return ENXIO; 588 589 return LAYERFS_DO_BYPASS(vp, ap); 590 } 591 592 /* 593 * We need to process our own vnode lock and then clear the 594 * interlock flag as it applies only to our vnode, not the 595 * vnodes below us on the stack. 596 */ 597 int 598 layer_lock(v) 599 void *v; 600 { 601 struct vop_lock_args /* { 602 struct vnode *a_vp; 603 int a_flags; 604 struct proc *a_p; 605 } */ *ap = v; 606 struct vnode *vp = ap->a_vp, *lowervp; 607 int flags = ap->a_flags, error; 608 609 if (vp->v_vnlock != NULL) { 610 /* 611 * The lower level has exported a struct lock to us. Use 612 * it so that all vnodes in the stack lock and unlock 613 * simultaneously. Note: we don't DRAIN the lock as DRAIN 614 * decommissions the lock - just because our vnode is 615 * going away doesn't mean the struct lock below us is. 616 * LK_EXCLUSIVE is fine. 617 */ 618 if ((flags & LK_TYPE_MASK) == LK_DRAIN) { 619 return(lockmgr(vp->v_vnlock, 620 (flags & ~LK_TYPE_MASK) | LK_EXCLUSIVE, 621 &vp->v_interlock)); 622 } else 623 return(lockmgr(vp->v_vnlock, flags, &vp->v_interlock)); 624 } else { 625 /* 626 * Ahh well. It would be nice if the fs we're over would 627 * export a struct lock for us to use, but it doesn't. 628 * 629 * To prevent race conditions involving doing a lookup 630 * on "..", we have to lock the lower node, then lock our 631 * node. Most of the time it won't matter that we lock our 632 * node (as any locking would need the lower one locked 633 * first). But we can LK_DRAIN the upper lock as a step 634 * towards decomissioning it. 635 */ 636 lowervp = LAYERVPTOLOWERVP(vp); 637 if (flags & LK_INTERLOCK) { 638 simple_unlock(&vp->v_interlock); 639 flags &= ~LK_INTERLOCK; 640 } 641 if ((flags & LK_TYPE_MASK) == LK_DRAIN) { 642 error = VOP_LOCK(lowervp, 643 (flags & ~LK_TYPE_MASK) | LK_EXCLUSIVE); 644 } else 645 error = VOP_LOCK(lowervp, flags); 646 if (error) 647 return (error); 648 if ((error = lockmgr(&vp->v_lock, flags, &vp->v_interlock))) { 649 VOP_UNLOCK(lowervp, 0); 650 } 651 return (error); 652 } 653 } 654 655 /* 656 */ 657 int 658 layer_unlock(v) 659 void *v; 660 { 661 struct vop_unlock_args /* { 662 struct vnode *a_vp; 663 int a_flags; 664 struct proc *a_p; 665 } */ *ap = v; 666 struct vnode *vp = ap->a_vp; 667 int flags = ap->a_flags; 668 669 if (vp->v_vnlock != NULL) { 670 return (lockmgr(vp->v_vnlock, ap->a_flags | LK_RELEASE, 671 &vp->v_interlock)); 672 } else { 673 if (flags & LK_INTERLOCK) { 674 simple_unlock(&vp->v_interlock); 675 flags &= ~LK_INTERLOCK; 676 } 677 VOP_UNLOCK(LAYERVPTOLOWERVP(vp), flags); 678 return (lockmgr(&vp->v_lock, ap->a_flags | LK_RELEASE, 679 &vp->v_interlock)); 680 } 681 } 682 683 /* 684 * As long as genfs_nolock is in use, don't call VOP_ISLOCKED(lowervp) 685 * if vp->v_vnlock == NULL as genfs_noislocked will always report 0. 686 */ 687 int 688 layer_islocked(v) 689 void *v; 690 { 691 struct vop_islocked_args /* { 692 struct vnode *a_vp; 693 } */ *ap = v; 694 struct vnode *vp = ap->a_vp; 695 696 if (vp->v_vnlock != NULL) 697 return (lockstatus(vp->v_vnlock)); 698 else 699 return (lockstatus(&vp->v_lock)); 700 } 701 702 /* 703 * If vinvalbuf is calling us, it's a "shallow fsync" -- don't bother 704 * syncing the underlying vnodes, since they'll be fsync'ed when 705 * reclaimed; otherwise, 706 * pass it through to the underlying layer. 707 * 708 * XXX Do we still need to worry about shallow fsync? 709 */ 710 711 int 712 layer_fsync(v) 713 void *v; 714 { 715 struct vop_fsync_args /* { 716 struct vnode *a_vp; 717 struct ucred *a_cred; 718 int a_flags; 719 struct proc *a_p; 720 } */ *ap = v; 721 722 if (ap->a_flags & FSYNC_RECLAIM) { 723 return 0; 724 } 725 726 return (LAYERFS_DO_BYPASS(ap->a_vp, ap)); 727 } 728 729 730 int 731 layer_inactive(v) 732 void *v; 733 { 734 struct vop_inactive_args /* { 735 struct vnode *a_vp; 736 struct proc *a_p; 737 } */ *ap = v; 738 739 /* 740 * Do nothing (and _don't_ bypass). 741 * Wait to vrele lowervp until reclaim, 742 * so that until then our layer_node is in the 743 * cache and reusable. 744 * 745 * NEEDSWORK: Someday, consider inactive'ing 746 * the lowervp and then trying to reactivate it 747 * with capabilities (v_id) 748 * like they do in the name lookup cache code. 749 * That's too much work for now. 750 */ 751 VOP_UNLOCK(ap->a_vp, 0); 752 return (0); 753 } 754 755 int 756 layer_reclaim(v) 757 void *v; 758 { 759 struct vop_reclaim_args /* { 760 struct vnode *a_vp; 761 struct proc *a_p; 762 } */ *ap = v; 763 struct vnode *vp = ap->a_vp; 764 struct layer_mount *lmp = MOUNTTOLAYERMOUNT(vp->v_mount); 765 struct layer_node *xp = VTOLAYER(vp); 766 struct vnode *lowervp = xp->layer_lowervp; 767 768 /* 769 * Note: in vop_reclaim, the node's struct lock has been 770 * decomissioned, so we have to be careful about calling 771 * VOP's on ourself. Even if we turned a LK_DRAIN into an 772 * LK_EXCLUSIVE in layer_lock, we still must be careful as VXLOCK is 773 * set. 774 */ 775 /* After this assignment, this node will not be re-used. */ 776 if ((vp == lmp->layerm_rootvp)) { 777 /* 778 * Oops! We no longer have a root node. Most likely reason is 779 * that someone forcably unmunted the underlying fs. 780 * 781 * Now getting the root vnode will fail. We're dead. :-( 782 */ 783 lmp->layerm_rootvp = NULL; 784 } 785 xp->layer_lowervp = NULL; 786 simple_lock(&lmp->layerm_hashlock); 787 LIST_REMOVE(xp, layer_hash); 788 simple_unlock(&lmp->layerm_hashlock); 789 FREE(vp->v_data, M_TEMP); 790 vp->v_data = NULL; 791 vrele (lowervp); 792 return (0); 793 } 794 795 /* 796 * We just feed the returned vnode up to the caller - there's no need 797 * to build a layer node on top of the node on which we're going to do 798 * i/o. :-) 799 */ 800 int 801 layer_bmap(v) 802 void *v; 803 { 804 struct vop_bmap_args /* { 805 struct vnode *a_vp; 806 daddr_t a_bn; 807 struct vnode **a_vpp; 808 daddr_t *a_bnp; 809 int *a_runp; 810 } */ *ap = v; 811 struct vnode *vp; 812 813 ap->a_vp = vp = LAYERVPTOLOWERVP(ap->a_vp); 814 815 return (VCALL(vp, ap->a_desc->vdesc_offset, ap)); 816 } 817 818 int 819 layer_print(v) 820 void *v; 821 { 822 struct vop_print_args /* { 823 struct vnode *a_vp; 824 } */ *ap = v; 825 struct vnode *vp = ap->a_vp; 826 printf ("\ttag VT_LAYERFS, vp=%p, lowervp=%p\n", vp, LAYERVPTOLOWERVP(vp)); 827 return (0); 828 } 829 830 /* 831 * XXX - vop_strategy must be hand coded because it has no 832 * vnode in its arguments. 833 * This goes away with a merged VM/buffer cache. 834 */ 835 int 836 layer_strategy(v) 837 void *v; 838 { 839 struct vop_strategy_args /* { 840 struct buf *a_bp; 841 } */ *ap = v; 842 struct buf *bp = ap->a_bp; 843 int error; 844 struct vnode *savedvp; 845 846 savedvp = bp->b_vp; 847 bp->b_vp = LAYERVPTOLOWERVP(bp->b_vp); 848 849 error = VOP_STRATEGY(bp); 850 851 bp->b_vp = savedvp; 852 853 return (error); 854 } 855 856 /* 857 * XXX - like vop_strategy, vop_bwrite must be hand coded because it has no 858 * vnode in its arguments. 859 * This goes away with a merged VM/buffer cache. 860 */ 861 int 862 layer_bwrite(v) 863 void *v; 864 { 865 struct vop_bwrite_args /* { 866 struct buf *a_bp; 867 } */ *ap = v; 868 struct buf *bp = ap->a_bp; 869 int error; 870 struct vnode *savedvp; 871 872 savedvp = bp->b_vp; 873 bp->b_vp = LAYERVPTOLOWERVP(bp->b_vp); 874 875 error = VOP_BWRITE(bp); 876 877 bp->b_vp = savedvp; 878 879 return (error); 880 } 881