1. 20 10月, 2008 1 次提交
  2. 14 10月, 2008 1 次提交
    • J
      ocfs2: Switch over to JBD2. · 2b4e30fb
      Joel Becker 提交于
      ocfs2 wants JBD2 for many reasons, not the least of which is that JBD is
      limiting our maximum filesystem size.
      
      It's a pretty trivial change.  Most functions are just renamed.  The
      only functional change is moving to Jan's inode-based ordered data mode.
      It's better, too.
      
      Because JBD2 reads and writes JBD journals, this is compatible with any
      existing filesystem.  It can even interact with JBD-based ocfs2 as long
      as the journal is formated for JBD.
      
      We provide a compatibility option so that paranoid people can still use
      JBD for the time being.  This will go away shortly.
      
      [ Moved call of ocfs2_begin_ordered_truncate() from ocfs2_delete_inode() to
        ocfs2_truncate_for_delete(). --Mark ]
      Signed-off-by: NJoel Becker <joel.becker@oracle.com>
      Signed-off-by: NMark Fasheh <mfasheh@suse.com>
      2b4e30fb
  3. 13 10月, 2008 2 次提交
  4. 11 10月, 2008 1 次提交
  5. 30 9月, 2008 2 次提交
    • C
      SUNRPC: Support IPv6 when registering kernel RPC services · a26cfad6
      Chuck Lever 提交于
      In order to advertise NFS-related services on IPv6 interfaces via
      rpcbind, the kernel RPC server implementation must use
      rpcb_v4_register() instead of rpcb_register().
      
      A new kernel build option allows distributions to use the legacy
      v2 call until they integrate an appropriate user-space rpcbind
      daemon that can support IPv6 RPC services.
      
      I tried adding some automatic logic to fall back if registering
      with a v4 protocol request failed, but there are too many corner
      cases.  So I just made it a compile-time switch that distributions
      can throw when they've replaced portmapper with rpcbind.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      a26cfad6
    • T
      Configure out file locking features · bfcd17a6
      Thomas Petazzoni 提交于
      This patch adds the CONFIG_FILE_LOCKING option which allows to remove
      support for advisory locks. With this patch enabled, the flock()
      system call, the F_GETLK, F_SETLK and F_SETLKW operations of fcntl()
      and NFS support are disabled. These features are not necessarly needed
      on embedded systems. It allows to save ~11 Kb of kernel code and data:
      
         text          data     bss     dec     hex filename
      1125436        118764  212992 1457192  163c28 vmlinux.old
      1114299        118564  212992 1445855  160fdf vmlinux
       -11137    -200       0  -11337   -2C49 +/-
      
      This patch has originally been written by Matt Mackall
      <mpm@selenic.com>, and is part of the Linux Tiny project.
      Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Signed-off-by: NMatt Mackall <mpm@selenic.com>
      Cc: matthew@wil.cx
      Cc: linux-fsdevel@vger.kernel.org
      Cc: mpm@selenic.com
      Cc: akpm@linux-foundation.org
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      bfcd17a6
  6. 27 8月, 2008 2 次提交
  7. 20 8月, 2008 1 次提交
  8. 27 7月, 2008 1 次提交
  9. 26 7月, 2008 2 次提交
  10. 15 7月, 2008 2 次提交
  11. 10 7月, 2008 2 次提交
    • C
      SUNRPC: Use only rpcbind v2 for AF_INET requests · 40fef8a6
      Chuck Lever 提交于
      Some server vendors support the higher versions of rpcbind only for
      AF_INET6.  The kernel doesn't need to use v3 or v4 for AF_INET anyway,
      so change the kernel's rpcbind client to query AF_INET servers over
      rpcbind v2 only.
      
      This has a few interesting benefits:
      
      1. If the rpcbind request is going over TCP, and the server doesn't
         support rpcbind versions 3 or 4, the client reduces by two the number
         of ephemeral ports left in TIME_WAIT for each rpcbind request.  This
         will help during NFS mount storms.
      
      2. The rpcbind interaction with servers that don't support rpcbind
         versions 3 or 4 will use less network traffic.  Also helpful
         during mount storms.
      
      3. We can eliminate the kernel build option that controls whether the
         kernel's rpcbind client uses rpcbind version 3 and 4 for AF_INET
         servers.  Less complicated kernel configuration...
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      40fef8a6
    • C
      NFS: Update help text for CONFIG_NFS_FS · 6fb1bc10
      Chuck Lever 提交于
      Clean up: refresh the help text for Kconfig items related to the NFS
      client.  Remove obsolete URLs, and make the language consistent among
      the options.
      
      Also move the ROOT_NFS config option next to the options related to the
      NFS client.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      6fb1bc10
  12. 08 7月, 2008 1 次提交
  13. 05 7月, 2008 1 次提交
  14. 30 4月, 2008 1 次提交
  15. 24 4月, 2008 8 次提交
  16. 18 4月, 2008 1 次提交
  17. 17 4月, 2008 1 次提交
  18. 12 4月, 2008 1 次提交
  19. 20 3月, 2008 3 次提交
  20. 08 2月, 2008 2 次提交
  21. 06 2月, 2008 1 次提交
  22. 02 2月, 2008 1 次提交
  23. 29 1月, 2008 1 次提交
    • G
      ext4: Add the journal checksum feature · 818d276c
      Girish Shilamkar 提交于
      The journal checksum feature adds two new flags i.e
      JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT and JBD2_FEATURE_COMPAT_CHECKSUM.
      
      JBD2_FEATURE_CHECKSUM flag indicates that the commit block contains the
      checksum for the blocks described by the descriptor blocks.
      Due to checksums, writing of the commit record no longer needs to be
      synchronous. Now commit record can be sent to disk without waiting for
      descriptor blocks to be written to disk. This behavior is controlled
      using JBD2_FEATURE_ASYNC_COMMIT flag. Older kernels/e2fsck should not be
      able to recover the journal with _ASYNC_COMMIT hence it is made
      incompat.
      The commit header has been extended to hold the checksum along with the
      type of the checksum.
      
      For recovery in pass scan checksums are verified to ensure the sanity
      and completeness(in case of _ASYNC_COMMIT) of every transaction.
      Signed-off-by: NAndreas Dilger <adilger@clusterfs.com>
      Signed-off-by: NGirish Shilamkar <girish@clusterfs.com>
      Signed-off-by: NDave Kleikamp <shaggy@linux.vnet.ibm.com>
      Signed-off-by: NMingming Cao <cmm@us.ibm.com>
      818d276c
  24. 26 1月, 2008 1 次提交