Searched hist:"68 d93184352f2e723f135b0a9bad93b58f9d120b" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/fs/nfsd/ |
| H A D | export.c | diff 68d93184352f2e723f135b0a9bad93b58f9d120b Fri Apr 08 16:00:50 CDT 2011 J. Bruce Fields <bfields@redhat.com> nfsd4: fix wrongsec handling for PUTFH + op cases
When PUTFH is followed by an operation that uses the filehandle, and
when the current client is using a security flavor that is inconsistent
with the given filehandle, we have a choice: we can return WRONGSEC
either when the current filehandle is set using the PUTFH, or when the
filehandle is first used by the following operation.
Follow the recommendations of RFC 5661 in making this choice.
(Our current behavior prevented the client from doing security
negotiation by returning WRONGSEC on PUTFH+SECINFO_NO_NAME.)
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
|
| H A D | nfs4proc.c | diff 68d93184352f2e723f135b0a9bad93b58f9d120b Fri Apr 08 16:00:50 CDT 2011 J. Bruce Fields <bfields@redhat.com> nfsd4: fix wrongsec handling for PUTFH + op cases
When PUTFH is followed by an operation that uses the filehandle, and
when the current client is using a security flavor that is inconsistent
with the given filehandle, we have a choice: we can return WRONGSEC
either when the current filehandle is set using the PUTFH, or when the
filehandle is first used by the following operation.
Follow the recommendations of RFC 5661 in making this choice.
(Our current behavior prevented the client from doing security
negotiation by returning WRONGSEC on PUTFH+SECINFO_NO_NAME.)
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
|