summaryrefslogtreecommitdiffstats
path: root/mm/bounce.c
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2013-05-15 17:34:39 -0400
committerJ. Bruce Fields <bfields@redhat.com>2013-07-01 17:23:06 -0400
commitb78724b70599f66a91c6d6c897a81f4f87f549f4 (patch)
tree52b9f29bf6122fa54e0f498585ccaa752af96818 /mm/bounce.c
parent57266a6e916e2522ea61758a3ee5576b60156791 (diff)
downloadblackbird-obmc-linux-b78724b70599f66a91c6d6c897a81f4f87f549f4.tar.gz
blackbird-obmc-linux-b78724b70599f66a91c6d6c897a81f4f87f549f4.zip
nfsd4: fail attempts to request gss on the backchannel
We don't support gss on the backchannel. We should state that fact up front rather than just letting things continue and later making the client try to figure out why the backchannel isn't working. Trond suggested instead returning NFS4ERR_NOENT. I think it would be tricky for the client to distinguish between the case "I don't support gss on the backchannel" and "I can't find that in my cache, please create another context and try that instead", and I'd prefer something that currently doesn't have any other meaning for this operation, hence the (somewhat arbitrary) NFS4ERR_ENCR_ALG_UNSUPP. Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'mm/bounce.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud