summaryrefslogtreecommitdiff
path: root/fs/nfsd/filecache.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@kernel.org>2022-12-13 21:08:26 +0300
committerChuck Lever <chuck.lever@oracle.com>2023-01-02 18:45:31 +0300
commitcad853374d85fe678d721512cecfabd7636e51f3 (patch)
tree6f45758852521e233d2b1bee4dca076ff8feb997 /fs/nfsd/filecache.c
parent789e1e10f214c00ca18fc6610824c5b9876ba5f2 (diff)
downloadlinux-cad853374d85fe678d721512cecfabd7636e51f3.tar.xz
nfsd: fix handling of readdir in v4root vs. mount upcall timeout
If v4 READDIR operation hits a mountpoint and gets back an error, then it will include that entry in the reply and set RDATTR_ERROR for it to the error. That's fine for "normal" exported filesystems, but on the v4root, we need to be more careful to only expose the existence of dentries that lead to exports. If the mountd upcall times out while checking to see whether a mountpoint on the v4root is exported, then we have no recourse other than to fail the whole operation. Cc: Steve Dickson <steved@redhat.com> Link: https://bugzilla.kernel.org/show_bug.cgi?id=216777 Reported-by: JianHong Yin <yin-jianhong@163.com> Signed-off-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Cc: <stable@vger.kernel.org>
Diffstat (limited to 'fs/nfsd/filecache.c')
0 files changed, 0 insertions, 0 deletions