nfsd4: don't continue "under" mounts in V4ROOT case
If /A/mount/point/ has filesystem "B" mounted on top of it, and if "A" is exported, but not "B", then the nfs server has always returned to the client a filehandle for the mountpoint, instead of for the root of "B", allowing the client to see the subtree of "A" that would otherwise be hidden by B. Disable this behavior in the case of V4ROOT exports; we implement the path restrictions of V4ROOT exports by treating *every* directory as if it were a mountpoint, and allowing traversal *only* if the new directory is exported. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
This commit is contained in:
parent
eb4c86c6a5
commit
3b6cee7bc4
1 changed files with 10 additions and 2 deletions
|
@ -99,8 +99,16 @@ nfsd_cross_mnt(struct svc_rqst *rqstp, struct dentry **dpp,
|
|||
|
||||
exp2 = rqst_exp_get_by_name(rqstp, &path);
|
||||
if (IS_ERR(exp2)) {
|
||||
if (PTR_ERR(exp2) != -ENOENT)
|
||||
err = PTR_ERR(exp2);
|
||||
err = PTR_ERR(exp2);
|
||||
/*
|
||||
* We normally allow NFS clients to continue
|
||||
* "underneath" a mountpoint that is not exported.
|
||||
* The exception is V4ROOT, where no traversal is ever
|
||||
* allowed without an explicit export of the new
|
||||
* directory.
|
||||
*/
|
||||
if (err == -ENOENT && !(exp->ex_flags & NFSEXP_V4ROOT))
|
||||
err = 0;
|
||||
path_put(&path);
|
||||
goto out;
|
||||
}
|
||||
|
|
Reference in a new issue