From: J. Bruce Fields Date: Fri, 20 Jun 2014 15:52:21 +0000 (-0400) Subject: nfsd: let nfsd_symlink assume null-terminated data X-Git-Tag: omap-for-v3.17/fixes-against-rc2~101^2~154 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=52ee04330f585d1b5bc40442f07df07248fa3aee;p=pandora-kernel.git nfsd: let nfsd_symlink assume null-terminated data Currently nfsd_symlink has a weird hack to serve callers who don't null-terminate symlink data: it looks ahead at the next byte to see if it's zero, and copies it to a new buffer to null-terminate if not. That means callers don't have to null-terminate, but they *do* have to ensure that the byte following the end of the data is theirs to read. That's a bit subtle, and the NFSv4 code actually got this wrong. So let's just throw out that code and let callers pass null-terminated strings; we've already fixed them to do that. Signed-off-by: J. Bruce Fields --- Reading git-diff-tree failed