1. 07 2月, 2012 1 次提交
  2. 13 1月, 2012 1 次提交
  3. 04 8月, 2011 1 次提交
    • T
      NFSv4.1: Fix the callback 'highest_used_slotid' behaviour · 55a67399
      Trond Myklebust 提交于
      Currently, there is no guarantee that we will call nfs4_cb_take_slot() even
      though nfs4_callback_compound() will consistently call
      nfs4_cb_free_slot() provided the cb_process_state has set the 'clp' field.
      The result is that we can trigger the BUG_ON() upon the next call to
      nfs4_cb_take_slot().
      
      This patch fixes the above problem by using the slot id that was taken in
      the CB_SEQUENCE operation as a flag for whether or not we need to call
      nfs4_cb_free_slot().
      It also fixes an atomicity problem: we need to set tbl->highest_used_slotid
      atomically with the check for NFS4_SESSION_DRAINING, otherwise we end up
      racing with the various tests in nfs4_begin_drain_session().
      
      Cc: stable@kernel.org [2.6.38+]
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      55a67399
  4. 30 5月, 2011 1 次提交
    • M
      pnfs: CB_NOTIFY_DEVICEID · 1be5683b
      Marc Eshel 提交于
      Note: This functionlaity is incomplete as all layout segments referring to
      the 'to be removed device id' need to be reaped, and all in flight I/O drained.
      
      [use be32 res in nfs4_callback_devicenotify]
      [use nfs_client to qualify deviceid for cb_notify_deviceid]
      [use global deviceid cache for CB_NOTIFY_DEVICEID]
      [refactor device cache _lookup_deviceid]
      [refactor device cache _find_get_deviceid]
      Signed-off-by: NBenny Halevy <bhalevy@panasas.com>
      [Bug in new global-device-cache code]
      [layout_driver MUST set free_deviceid_node if using dev-cache]
      Signed-off-by: NBoaz Harrosh <bharrosh@panasas.com>
      Signed-off-by: NBenny Halevy <bhalevy@panasas.com>
      1be5683b
  5. 26 1月, 2011 1 次提交
  6. 07 1月, 2011 5 次提交
  7. 10 2月, 2010 1 次提交
  8. 06 12月, 2009 2 次提交
  9. 18 6月, 2009 10 次提交
  10. 29 3月, 2009 1 次提交
    • C
      NFS: Start PF_INET6 callback listener only if IPv6 support is available · f738f517
      Chuck Lever 提交于
      Apparently a lot of people need to disable IPv6 completely on their
      distributor-built systems, which have CONFIG_IPV6_MODULE enabled at
      build time.
      
      They do this by blacklisting the ipv6.ko module.  This causes the
      creation of the NFSv4 callback service listener to fail if
      CONFIG_IPV6_MODULE is set, but the module cannot be loaded.
      
      Now that the kernel's PF_INET6 RPC listeners are completely separate
      from PF_INET listeners, we can always start PF_INET.  Then the NFS
      client can try to start a PF_INET6 listener, but it isn't required
      to be available.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      f738f517
  11. 30 1月, 2008 2 次提交
  12. 15 5月, 2007 1 次提交
    • T
      NFS: Fix more sparse warnings · 2e42c3e2
      Trond Myklebust 提交于
       - fs/nfs/nfs4xdr.c:2499:42: warning: incorrect type in argument 2
         (different signedness)
       - fs/nfs/nfs4xdr.c:2658:49: warning: incorrect type in argument 4
         (different explicit signedness)
       - fs/nfs/nfs4xdr.c:2683:50: warning: incorrect type in argument 4
         (different explicit signedness)
       - fs/nfs/nfs4xdr.c:3063:68: warning: incorrect type in argument 4
         (different explicit signedness)
       - fs/nfs/nfs4xdr.c:3065:68: warning: incorrect type in argument 4
         (different explicit signedness)
      
       - fs/nfs/callback_xdr.c:138:31: warning: incorrect type in argument 2
         (different signedness)
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      2e42c3e2
  13. 21 10月, 2006 2 次提交
  14. 23 9月, 2006 1 次提交
  15. 07 1月, 2006 1 次提交
  16. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4