Andreas Dilger wrote:
> Upgrade your kernel before reporting such bugs. I'm pretty sure it has
> already been fixed. Something about the NFSv3 calling an inappropriate
> (but similarly named) function in the symlink path.
I've looked at the 2.4.14 nfs fs code as it seemed client side.
/* We place the length at the beginning of the page,
* in host byte order, followed by the string. The
* XDR response verification will NULL terminate it.
*/
I'm guessing nfs3xdr.c does not have this behaviour the code relies on. I
will grab 2.4.17 and see of the code/behaviour is different.
--
www.kuro5hin.org -- technology and culture, from the trenches.
-=-=-=-=-=-
Those that give up liberty to obtain safety deserve neither.
-- Benjamin Franklin
http://www.zdnet.com/zdnn/stories/news/0,4586,2812463,00.html
http://slashdot.org/article.pl?sid=01/09/16/1647231
-=-=-=-=-=-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jan 15 2002 - 21:00:48 EST