NFSv4.1: Make sure nfsd can decode SP4_SSV correctly at exchange_id
authorMi Jinlong <mijinlong@cn.fujitsu.com>
Tue, 9 Nov 2010 01:39:23 +0000 (09:39 +0800)
committerJ. Bruce Fields <bfields@redhat.com>
Fri, 19 Nov 2010 23:35:12 +0000 (18:35 -0500)
commit5afa040b307952bb804eba34b21646da2842e14d
tree3c7b1c14f3a9bb1a3a438d7f116be358ff4310e8
parent9c335c0b8daf56b9f73479d00b1dd726e1fcca09
NFSv4.1: Make sure nfsd can decode SP4_SSV correctly at exchange_id

According to RFC, the argument of ssv_sp_parms4 is:

   struct ssv_sp_parms4 {
           state_protect_ops4      ssp_ops;
           sec_oid4                ssp_hash_algs<>;
           sec_oid4                ssp_encr_algs<>;
           uint32_t                ssp_window;
           uint32_t                ssp_num_gss_handles;
   };

If client send a exchange_id with SP4_SSV, server cann't decode
the SP4_SSV's ssp_hash_algs and ssp_encr_algs arguments correctly.

Because the kernel treat the two arguments as a signal
sec_oid4 struct, but should be a set of sec_oid4 struct.

Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4xdr.c