make nfsd's setclientid behavior migration-friendly
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | nfsd: randomize SETCLIENTID reply to help distinguish serversfs/ | +2 | 0 replies | |
| 2/2 | nfsd4: setclientid_confirm with unmatched verifier should failfs/ | +3 | 0 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Jeff Layton |
|---|---|
| Series | R-b A-b |
| 1/2 | |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [0/2] make nfsd's setclientid behavior migration-friendly
Clients mounting multiple servers with the "migration" option may find some mounts are made from the incorrect server.
I think this is really a bug in RFC 7931, and that RFC and the client need fixing, but this is easy to mitigate on the server. I'll make an attempt at a client patch too.
--b.