cvs commit: src/sbin/mount_null mount_null.c src/sys/kern vfs_bio.c vfs_cache.c vfs_mount.c vfs_nlookup.c vfs_syscalls.c src/sys/sys mount.h namecache.h vnode.h src/sys/vfs/nfs nfs_serv.c nfs_vfsops.c src/sys/vfs/ufs ufs_vnops.c src/sys/vfs/union ...

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxxxxx>]

dillon      2006/09/19 09:06:17 PDT

DragonFly src repository

  Modified files:
    sbin/mount_null      mount_null.c 
    sys/kern             vfs_bio.c vfs_cache.c vfs_mount.c 
                         vfs_nlookup.c vfs_syscalls.c 
    sys/sys              mount.h namecache.h vnode.h 
    sys/vfs/nfs          nfs_serv.c nfs_vfsops.c 
    sys/vfs/ufs          ufs_vnops.c 
    sys/vfs/union        union_vfsops.c 
  Log:
  Remove the last bits of code that stored mount point linkages in vnodes.
  Mount point linkages are now ENTIRELY a function of the namecache topology,
  made possible by DragonFly's advanced namecache.
  
  This fixes a number of problems with NULLFS and adds two major features to
  our NULLFS mounting capabilities.
  
  NULLFS mounting paths NO LONGER NEED TO BE DISTINCT.  For example, you
  can now safely do things like 'mount_null -o ro / /fubar/jail1' without
  creating a recursion and you can now create SUB-MOUNTS within nullfs
  mounts, such as 'mount_null -o ro /usr /fubar/jail1/usr', without creating
  problems in the original master partitions.
  
  The result is that NULLFS can now be used to glue arbitrary pieces of
  filesystems together using a mixture of read-only and read-write NULLFS
  mounts for situations where localhost NFS mounts had to be used before.
  Jail or chroot construction is now utterly trivial.
  
  With-input-from: Joerg Sonnenberger <joerg@xxxxxxxxxxxxxxxxx>
  
  Revision  Changes    Path
  1.8       +7 -4      src/sbin/mount_null/mount_null.c
  1.81      +2 -2      src/sys/kern/vfs_bio.c
  1.77      +46 -0     src/sys/kern/vfs_cache.c
  1.23      +0 -1      src/sys/kern/vfs_mount.c
  1.19      +7 -3      src/sys/kern/vfs_nlookup.c
  1.105     +47 -17    src/sys/kern/vfs_syscalls.c
  1.29      +1 -1      src/sys/sys/mount.h
  1.27      +5 -1      src/sys/sys/namecache.h
  1.71      +1 -3      src/sys/sys/vnode.h
  1.40      +2 -2      src/sys/vfs/nfs/nfs_serv.c
  1.47      +0 -1      src/sys/vfs/nfs/nfs_vfsops.c
  1.57      +0 -4      src/sys/vfs/ufs/ufs_vnops.c
  1.27      +1 -2      src/sys/vfs/union/union_vfsops.c


http://www.dragonflybsd.org/cvsweb/src/sbin/mount_null/mount_null.c.diff?r1=1.7&r2=1.8&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/vfs_bio.c.diff?r1=1.80&r2=1.81&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/vfs_cache.c.diff?r1=1.76&r2=1.77&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/vfs_mount.c.diff?r1=1.22&r2=1.23&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/vfs_nlookup.c.diff?r1=1.18&r2=1.19&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/vfs_syscalls.c.diff?r1=1.104&r2=1.105&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/sys/mount.h.diff?r1=1.28&r2=1.29&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/sys/namecache.h.diff?r1=1.26&r2=1.27&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/sys/vnode.h.diff?r1=1.70&r2=1.71&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/vfs/nfs/nfs_serv.c.diff?r1=1.39&r2=1.40&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/vfs/nfs/nfs_vfsops.c.diff?r1=1.46&r2=1.47&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/vfs/ufs/ufs_vnops.c.diff?r1=1.56&r2=1.57&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/vfs/union/union_vfsops.c.diff?r1=1.26&r2=1.27&f=u