the NFSv2/NFSv3 server does not handle zero length WRITE requests correctly
Subsystems (2)
PATCH 1/1 the NFSv2/NFSv3 server does not handle zero length WRITE requests correctly
Hi.
The NFSv2 and NFSv3 servers do not handle WRITE requests for 0 bytes correctly. The specifications indicate that the server should accept the request, but it should mostly turn into a no-op. Currently, the server will return an XDR decode error, which it should not.
Attached is a patch which addresses this issue. It also adds some boundary checking to ensure that the request contains as much data as was requested to be written. It also correctly handles an NFSv3 request which requests to write more data than the server has stated that it is prepared to handle. Previously, there was some support which looked like it should work, but wasn't quite right.
Questions or comments?
Thanx...
ps
fs/nfsd/nfsxdr.c renamed from fs/nfsd/nfsxdr.c.org +39 -7
@@ -271,8 +271,9 @@ int nfssvc_decode_writeargs(struct svc_rqst *rqstp, __be32 *p, struct nfsd_writeargs *args) { - unsigned int len; + unsigned int len, hdr, dlen;int v; +if (!(p =decode_fh (p, &args->fh)))return 0 ;
@@ -280,11 +281,42 @@ nfssvc_decode_writeargs(struct svc_rqst args->offset =ntohl (*p++);/* offset */ p++;/* totalcount */ len = args->len =ntohl (*p++); - rqstp->rq_vec[0 ].iov_base = (void *)p; - rqstp->rq_vec[0 ].iov_len = rqstp->rq_arg.head[0 ].iov_len - - (((void *)p) - rqstp->rq_arg.head[0 ].iov_base); +/* +* The protocol specifies a maximum of 8192 bytes. +*/ if (len >NFSSVC_MAXBLKSIZE_V2 ) - len =NFSSVC_MAXBLKSIZE_V2 ; +return 0 ; + +/* +* Check to make sure that we got the right number of +* bytes. +* +* If more than one page was used, then compute the length +* of the data in the request as the total size of the +* request minus the transport protocol headers minus the +* RPC protocol headers minus the NFS protocol fields +* already consumed. If the request fits into a single +* page, then compete the length of the data as the size +* of the NFS portion of the request minus the NFS +* protocol fields already consumed. +*/ + hdr = (void *)p - rqstp->rq_arg.head[0 ].iov_base; +if (rqstp->rq_respages != rqstp->rq_pages +1 ) { + dlen = rqstp->rq_arg.len - + (PAGE_SIZE - rqstp->rq_arg.head[0 ].iov_len) - hdr; + }else { + dlen = rqstp->rq_arg.head[0 ].iov_len - hdr; + } +/* +* Round the length of the data which was specified up to +* the next multiple of XDR units and then compare that +* against the length which was actually received. +*/ +if (dlen != ((len +3 ) & ~0x3 )) +return 0 ; + + rqstp->rq_vec[0 ].iov_base = (void *)p; + rqstp->rq_vec[0 ].iov_len = rqstp->rq_arg.head[0 ].iov_len - hdr; v =0 ;while (len > rqstp->rq_vec[v].iov_len) { len -= rqstp->rq_vec[v].iov_len;
@@ -293,8 +325,8 @@ nfssvc_decode_writeargs(struct svc_rqst rqstp->rq_vec[v].iov_len =PAGE_SIZE ; } rqstp->rq_vec[v].iov_len = len; - args->vlen = v+1 ; -return rqstp->rq_vec[0 ].iov_len >0 ; + args->vlen = v +1 ; +return 1 ; }int
fs/nfsd/nfs3xdr.c renamed from fs/nfsd/nfs3xdr.c.org +38 -10
72 lines not on this page · raw message
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs