diff options
| author | Olga Kornievskaia <kolga@netapp.com> | 2024-05-29 22:44:35 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-06-21 15:38:28 +0300 |
| commit | c30988e06b155a8f09bbf6e6681f142471eec5a9 (patch) | |
| tree | 232ca4b01d6dc8120cd8010586552f96e0975b39 /net/bluetooth | |
| parent | a9aa5a49c8edf895bd5c4becdd359f7fcb2ea0ea (diff) | |
| download | linux-c30988e06b155a8f09bbf6e6681f142471eec5a9.tar.xz | |
NFSv4.1 enforce rootpath check in fs_location query
[ Upstream commit 28568c906c1bb5f7560e18082ed7d6295860f1c2 ]
In commit 4ca9f31a2be66 ("NFSv4.1 test and add 4.1 trunking transport"),
we introduce the ability to query the NFS server for possible trunking
locations of the existing filesystem. However, we never checked the
returned file system path for these alternative locations. According
to the RFC, the server can say that the filesystem currently known
under "fs_root" of fs_location also resides under these server
locations under the following "rootpath" pathname. The client cannot
handle trunking a filesystem that reside under different location
under different paths other than what the main path is. This patch
enforces the check that fs_root path and rootpath path in fs_location
reply is the same.
Fixes: 4ca9f31a2be6 ("NFSv4.1 test and add 4.1 trunking transport")
Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions