On Fri, 2013-09-06 at 14:14 -0400, andros@xxxxxxxxxx wrote:
> From: Andy Adamson <andros@xxxxxxxxxx>
>
> 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: Andy Adamson <andros@xxxxxxxxxx>
> ---
>
Thank you Andy! Unless something comes up, I'm applying this one.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
