1. 16 5月, 2006 1 次提交
    • A
      [PATCH] revert "vfs: propagate mnt_flags into do_loopback/vfsmount" · eee391a6
      Andrew Morton 提交于
      Revert commit f6422f17, due to
      
      Valdis.Kletnieks@vt.edu wrote:
      >
      > There seems to have been a bug introduced in this changeset:
      >
      > Am running 2.6.17-rc3-mm1.  When this changeset is applied, 'mount --bind'
      > misbehaves:
      >
      > > # mkdir /foo
      > > # mount -t tmpfs -o rw,nosuid,nodev,noexec,noatime,nodiratime none /foo
      > > # mkdir /foo/bar
      > > # mount --bind /foo/bar /foo
      > > # tail -2 /proc/mounts
      > > none /foo tmpfs rw,nosuid,nodev,noexec,noatime,nodiratime 0 0
      > > none /foo tmpfs rw 0 0
      >
      > Reverting this changeset causes both mounts to have the same options.
      >
      > (Thanks to Stephen Smalley for tracking down the changeset...)
      >
      
      Cc: Herbert Poetzl <herbert@13thfloor.at>
      Cc: Christoph Hellwig <hch@infradead.org>
      Cc: <Valdis.Kletnieks@vt.edu>
      Cc: Stephen Smalley <sds@tycho.nsa.gov>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      eee391a6
  2. 11 4月, 2006 1 次提交
  3. 28 3月, 2006 1 次提交
  4. 27 3月, 2006 1 次提交
  5. 21 3月, 2006 1 次提交
    • C
      VFS: New /proc file /proc/self/mountstats · b4629fe2
      Chuck Lever 提交于
      Create a new file under /proc/self, called mountstats, where mounted file
      systems can export information (configuration options, performance counters,
      and so on).  Use a mechanism similar to /proc/mounts and s_ops->show_options.
      
      This mechanism does not violate namespace security, and is safe to use while
      other processes are unmounting file systems.
      
      Thanks to Mike Waychison for his review and comments.
      
      Test-plan:
      Test concurrent mount/unmount operations while cat'ing /proc/self/mountstats.
      Signed-off-by: NChuck Lever <cel@netapp.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      b4629fe2
  6. 16 3月, 2006 1 次提交
  7. 08 2月, 2006 2 次提交
  8. 17 1月, 2006 1 次提交
  9. 12 1月, 2006 1 次提交
  10. 11 1月, 2006 1 次提交
    • C
      [PATCH] per-mountpoint noatime/nodiratime · fc33a7bb
      Christoph Hellwig 提交于
      Turn noatime and nodiratime into per-mount instead of per-sb flags.
      
      After all the preparations this is a rather trivial patch.  The mount code
      needs to treat the two options as per-mount instead of per-superblock, and
      touch_atime needs to be changed to check the new MNT_ flags in addition to
      the MS_ flags that are kept for filesystems that are always
      noatime/nodiratime but not user settable anymore.  Besides that core code
      only nfs needed an update because it's leaving atime updates to the server
      and thus sets the S_NOATIME flag on every inode, but needs to know whether
      it's a real noatime mount for an getattr optimization.
      
      While we're at it I've killed the IS_NOATIME/IS_NODIRATIME macros that were
      only used by touch_atime.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      fc33a7bb
  11. 10 1月, 2006 1 次提交
  12. 09 1月, 2006 2 次提交
  13. 09 11月, 2005 1 次提交
  14. 08 11月, 2005 16 次提交
  15. 11 9月, 2005 1 次提交
  16. 08 9月, 2005 2 次提交
  17. 08 8月, 2005 1 次提交
    • M
      [PATCH] namespace.c: fix bind mount from foreign namespace · 68b47139
      Miklos Szeredi 提交于
      I'm resending this patch, because I still believe it's the correct fix.
      
      Tested before/after applying the patch with a test application
      available from:
      
        http://www.inf.bme.hu/~mszeredi/nstest.c
      
      Bind mount from a foreign namespace results in an un-removable mount.
      The reason is that mnt->mnt_namespace is copied from the old mount in
      clone_mnt().  Because of this check_mnt() in sys_umount() will fail.
      
      The solution is to set mnt->mnt_namespace to current->namespace in
      clone_mnt().  clone_mnt() is either called from do_loopback() or
      copy_tree().  copy_tree() is called from do_loopback() or
      copy_namespace().
      
      When called (directly or indirectly) from do_loopback(), always
      current->namspace is being modified: check_mnt(nd->mnt).  So setting
      mnt->mnt_namespace to current->namspace is the right thing to do.
      
      When called from copy_namespace(), the setting of mnt_namespace is
      irrelevant, since mnt_namespace is reset later in that function for
      all copied mounts.
      
      Jamie said:
      
        This patch is correct.  The old code was buggy for more fundamental and
        serious reason: it broke the invariant that a tree of vfsmnts all have the
        same value of mnt_namespace (and the same for the mnt_list list).
      Signed-off-by: NMiklos Szeredi <miklos@szeredi.hu>
      Acked-by: NJamie Lokier <jamie@shareable.org>
      Cc: <viro@parcelfarce.linux.theplanet.co.uk>
      Cc: Christoph Hellwig <hch@lst.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      68b47139
  18. 08 7月, 2005 5 次提交