> >> > > > > So the code as it stands violates the RFC by sending 2 chunks? > > The Linux client is non-compliant because it sends two chunks. A compliant server ignores the > second chunk, so this is functionally harmless (but a waste of resources). > > The Linux server is non-compliant because it _requires_ the XDR pad chunk. A compliant client > (eg. Linux with pad optimization enabled) does not interoperate with it. > > > And if I change the server > > to only consume 1, then everything unaligned will break? > > If you change the server to consume only the first chunk, but do not also make it deal with XDR > padding as recommended in chapter 3 of RFC 5666, then WRITEs with a length that is not a > multiple of four will fail. SYMLINKs with a large payload will also have this problem. > Thanks Chuck for clarifying this! So I'm going to defer this issue and fix it with a subsequent patch to only process 1 chunk and handle pad correctly. Steve. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
