Add secinfo to the NFS client
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest5 patches 1 replyIn review
- v25 patches 5 repliesSuperseded
Changes in v4 from the cover letter
- Properly set the number of security flavors decoded by the client
- Return an int rather than an rpc_authflavor_t for better error checking
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | NFS: convert call_sync() to a functionfs/ | +30 | 0 replies | |
| 2/5 | NFS: lookup supports alternate clientfs/ fs/ fs/ +5 more | +60 | 0 replies | |
| 3/5 | NFS: Add secinfo procedurefs/ fs/ include/ +1 more | +209 | 1 reply | |
| 4/5 | NFS: use secinfo when crossing mountpointsfs/ fs/ fs/ +4 more | +154 | 0 replies | |
| 5/5 | NFS: Determine initial mount securityfs/ include/ net/ | +50 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.
Cover letter [PATCH v4 0/5] Add secinfo to the NFS client
These patches will add the secinfo procedure to the NFS client and do some cleanup along the way. The final result will should be able to cross mountpoints using a different form of security and auto-detect the security of an initial NFS v4 mount.
v4:
- Properly set the number of security flavors decoded by the client
- Return an int rather than an rpc_authflavor_t for better error checking
v3:
- Check for server returning too many security flavors
- Check for gss_oid_len > max_gss_oid_len
- New functions in namespace.c should be static
v2:
- Add more details about the call_sync improvement
- Don't initialize global constant function pointers to NULL
Bryan