Bug 219581 - NFSv4.1 client recovery from NFSERR_BADSESSION errors from Solaris server
Summary: NFSv4.1 client recovery from NFSERR_BADSESSION errors from Solaris server
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: Rick Macklem
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-26 22:04 UTC by Rick Macklem
Modified: 2017-05-27 01:49 UTC (History)
1 user (show)

See Also:


Attachments
do CreateSession with extant ClientID first for BADSESSION recovery (6.91 KB, patch)
2017-05-26 22:04 UTC, Rick Macklem
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Macklem freebsd_committer 2017-05-26 22:04:26 UTC
Created attachment 182948 [details]
do CreateSession with extant ClientID first for BADSESSION recovery

Some NFSv4.1 servers return NFS4ERR_BAD_SESSION for cases where the ClientID
is still valid. I believe that Solaris servers do this.
As such, the recovery that starts with ExchangeID to acquire a new ClientID
is not correct for these servers.
This patch modifies the code so that it first attempts a CreateSession with
the extant ClientID and only does the ExchangeID, CreateSession recovery
if this fails.

I believe this is correct for Solaris servers, but since I do not have any
Solaris server to test against, I don't actually know if this patch works
for Solaris servers?