1. 07 Sep, 2013 4 commits
  2. 06 Sep, 2013 2 commits
    • Andy Adamson's avatar
      NFSv4.1 Use MDS auth flavor for data server connection · 0e20162e
      Andy Adamson authored
      Commit 4edaa308 "NFS: Use "krb5i" to establish NFSv4 state whenever possible"
      uses the nfs_client cl_rpcclient for all state management operations, and
      will use krb5i or auth_sys with no regard to the mount command authflavor
      choice.
      
      The MDS, as any NFSv4.1 mount point, uses the nfs_server rpc client for all
      non-state management operations with a different nfs_server for each fsid
      encountered traversing the mount point, each with a potentially different
      auth flavor.
      
      pNFS data servers are not mounted in the normal sense as there is no associated
      nfs_server structure. Data servers can also export multiple fsids, each with
      a potentially different auth flavor.
      
      Data servers need to use the same authflavor as the MDS server rpc client for
      non-state management operations. Populate a list of rpc clients with the MDS
      server rpc client auth flavor for the DS to use.
      Signed-off-by: default avatarAndy Adamson <andros@netapp.com>
      Signed-off-by: default avatarTrond Myklebust <Trond.Myklebust@netapp.com>
      0e20162e
    • Trond Myklebust's avatar
      NFS: Don't check lock owner compatability unless file is locked (part 2) · 4109bb74
      Trond Myklebust authored
      When coalescing requests into a single READ or WRITE RPC call, and there
      is no file locking involved, we don't have to refuse coalescing for
      requests where the lock owner information doesn't match.
      Reported-by: default avatarJeff Layton <jlayton@redhat.com>
      Signed-off-by: default avatarTrond Myklebust <Trond.Myklebust@netapp.com>
      4109bb74
  3. 05 Sep, 2013 10 commits
  4. 04 Sep, 2013 6 commits
  5. 03 Sep, 2013 18 commits