aboutsummaryrefslogtreecommitdiffstats
path: root/Kbuild
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@citi.umich.edu>2010-02-08 13:42:26 -0500
committerJ. Bruce Fields <bfields@citi.umich.edu>2010-02-08 15:25:23 -0500
commit260c64d23532caf19abb77e696971da05c388489 (patch)
tree75e0565f42f5e0639b5436c33470f67a591406b5 /Kbuild
parentb292cf9ce70d221c3f04ff62db5ab13d9a249ca8 (diff)
downloadkernel_samsung_aries-260c64d23532caf19abb77e696971da05c388489.zip
kernel_samsung_aries-260c64d23532caf19abb77e696971da05c388489.tar.gz
kernel_samsung_aries-260c64d23532caf19abb77e696971da05c388489.tar.bz2
Revert "nfsd4: fix error return when pseudoroot missing"
Commit f39bde24b275ddc45d fixed the error return from PUTROOTFH in the case where there is no pseudofilesystem. This is really a case we shouldn't hit on a correctly configured server: in the absence of a root filehandle, there's no point accepting version 4 NFS rpc calls at all. But the shared responsibility between kernel and userspace here means the kernel on its own can't eliminate the possiblity of this happening. And we have indeed gotten this wrong in distro's, so new client-side mount code that attempts to negotiate v4 by default first has to work around this case. Therefore when commit f39bde24b275ddc45d arrived at roughly the same time as the new v4-default mount code, which explicitly checked only for the previous error, the result was previously fine mounts suddenly failing. We'll fix both sides for now: revert the error change, and make the client-side mount workaround more robust. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions