On 09/15/2014 08:12 PM, Christoph Hellwig wrote: > On Mon, Sep 15, 2014 at 12:05:55PM +0300, Boaz Harrosh wrote: >> I do not understand. This used to work just fine. Please point me to >> the patch that broke it? >> (And since when are we allowed to brake old code?) > > I bet it still works the same way it does as commited, which doesn't > make it right. The way the NFS XDR buffer allocations work seems to be > that you can actually slightly overun it without things falling apart, > but that doesn't make it right. E.g. it took a fairly larger overrun > in the block layout driver to finally find the issues, and most of the > time it was just silent truncations, real corruption happened less > often. > > But to make sure things work properly in the long run you'd really want > to have the proper allocation. > Thanks Christoph for explaining. OK make sense what you said. Actually I know why it works. You know that extra page we have at nfs-xdr for if a struct spans two pages than the xdr code will memcpy it it a spare buffer contiguous and return that. Ha, no, that is for decoding. But I bet for encoding there is spare buffers as well. I will try to push for a two 64bit growth at the core reservation for pnf-obj. No point in adding a full page for extra 16 bytes. I bet it will not change anything because of the reserved space. I'm not familiar with this code, I'll try to find where core reservation is allocated for layout update? Thanks Boaz -- 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
