1. 21 2月, 2007 1 次提交
    • N
      [PATCH] fs: fix libfs data leak · 955eff5a
      Nick Piggin 提交于
      simple_prepare_write leaks uninitialised kernel data.  This happens because
      the it leaves an uninitialised "hole" over the part of the page that the
      write is expected to go to.  This is fine, but it then marks the page
      uptodate, which means a concurrent read can come in and copy the
      uninitialised memory into userspace before it written to.
      
      Fix it by simply marking it uptodate in simple_commit_write instead, after
      the hole has been filled in.  This could theoretically break an fs that
      uses simple_prepare_write and not simple_commit_write, and that relies on
      the incorrect simple_prepare_write behaviour.  Luckily, none of those
      exists in the tree.
      Signed-off-by: NNick Piggin <npiggin@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      955eff5a
  2. 19 2月, 2007 1 次提交
    • E
      9p: implement optional loose read cache · e03abc0c
      Eric Van Hensbergen 提交于
      While cacheing is generally frowned upon in the 9p world, it has its
      place -- particularly in situations where the remote file system is
      exclusive and/or read-only.  The vacfs views of venti content addressable
      store are a real-world instance of such a situation.  To facilitate higher
      performance for these workloads (and eventually use the fscache patches),
      we have enabled a "loose" cache mode which does not attempt to maintain
      any form of consistency on the page-cache or dcache.  This results in over
      two orders of magnitude performance improvement for cacheable block reads
      in the Bonnie benchmark.  The more aggressive use of the dcache also seems
      to improve metadata operational performance.
      Signed-off-by: NEric Van Hensbergen <ericvh@gmail.com>
      e03abc0c
  3. 18 2月, 2007 1 次提交
  4. 13 2月, 2007 1 次提交
    • E
      [PATCH] ufs2 write: mount as rw · cbcae39f
      Evgeniy Dushistov 提交于
      These series of patches add UFS2 write-support.  UFS2 - is default file system
      for recent versions of FreeBSD.
      
      The main differences from UFS1 from write support point of view
      are:
      1)Not all inodes are allocated during formatation of disk.
      2)All meta-data(pointer to data blocks) are 64bit(in UFS1 they
      are 32bit).
      
      So patch series consist of
      1)make possible mount UFS2 in read-write mode
      2)code to write ufs2 inodes and code to initialize inodes chunks.
      3)work with 64bit meta-data
      
      I made simple testing like create/deleting/writing/reading/truncating, also I
      ran fsx-linux and untar and build kernel on UFS1 and UFS2, after that FreeBSD
      fsck do not find any errors in fs.
      
      This patch makes possible to mount ufs2 "rw", and updates UFS2 documentation:
      remove note about bug(it fixed by reallocate blocks on the fly patch) and add
      me in the list of people who want receive bug reports.
      Signed-off-by: NEvgeniy Dushistov <dushistov@mail.ru>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cbcae39f
  5. 12 2月, 2007 1 次提交
  6. 27 1月, 2007 1 次提交
  7. 18 1月, 2007 1 次提交
  8. 12 1月, 2007 1 次提交
    • T
      [PATCH] NFS: Fix race in nfs_release_page() · e3db7691
      Trond Myklebust 提交于
          NFS: Fix race in nfs_release_page()
      
          invalidate_inode_pages2() may find the dirty bit has been set on a page
          owing to the fact that the page may still be mapped after it was locked.
          Only after the call to unmap_mapping_range() are we sure that the page
          can no longer be dirtied.
          In order to fix this, NFS has hooked the releasepage() method and tries
          to write the page out between the call to unmap_mapping_range() and the
          call to remove_mapping(). This, however leads to deadlocks in the page
          reclaim code, where the page may be locked without holding a reference
          to the inode or dentry.
      
          Fix is to add a new address_space_operation, launder_page(), which will
          attempt to write out a dirty page without releasing the page lock.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      
          Also, the bare SetPageDirty() can skew all sort of accounting leading to
          other nasties.
      
      [akpm@osdl.org: cleanup]
      Signed-off-by: NPeter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e3db7691
  9. 31 12月, 2006 1 次提交
  10. 14 12月, 2006 1 次提交
  11. 08 12月, 2006 5 次提交
  12. 30 11月, 2006 3 次提交
  13. 17 11月, 2006 1 次提交
  14. 12 10月, 2006 1 次提交
  15. 04 10月, 2006 11 次提交
  16. 01 10月, 2006 1 次提交
  17. 30 9月, 2006 1 次提交
  18. 26 9月, 2006 1 次提交
  19. 28 8月, 2006 1 次提交
  20. 11 7月, 2006 1 次提交
  21. 30 6月, 2006 1 次提交
  22. 27 6月, 2006 2 次提交
  23. 26 6月, 2006 1 次提交