diff options
| author | Jeff Layton <jlayton@poochiereds.net> | 2014-06-21 20:52:17 -0400 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@primarydata.com> | 2014-07-12 18:41:25 -0400 |
| commit | f11b2a1cfbf5dd783eb55cb470509d06e20d1c78 (patch) | |
| tree | 3e7ecb73670953ef7067551582dd3c432736a86c /fs/affs | |
| parent | a0337d1ddb5a4bd609e3ff0955551cb240340340 (diff) | |
| download | op-kernel-dev-f11b2a1cfbf5dd783eb55cb470509d06e20d1c78.zip op-kernel-dev-f11b2a1cfbf5dd783eb55cb470509d06e20d1c78.tar.gz | |
nfs4: copy acceptor name from context to nfs_client
The current CB_COMPOUND handling code tries to compare the principal
name of the request with the cl_hostname in the client. This is not
guaranteed to ever work, particularly if the client happened to mount
a CNAME of the server or a non-fqdn.
Fix this by instead comparing the cr_principal string with the acceptor
name that we get from gssd. In the event that gssd didn't send one
down (i.e. it was too old), then we fall back to trying to use the
cl_hostname as we do today.
Signed-off-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/affs')
0 files changed, 0 insertions, 0 deletions
