diff options
| author | Paulo Alcantara <pc@manguebit.com> | 2024-11-18 18:35:16 +0300 |
|---|---|---|
| committer | Steve French <stfrench@microsoft.com> | 2024-11-21 19:45:50 +0300 |
| commit | 0812340811e45ec4039d409049be53056182a552 (patch) | |
| tree | 5fd69d99e363091267f69811678d1ce8de67a9f9 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | 9f544d26b15bfc52cf3a6e6a655f759e76c1a01a (diff) | |
| download | linux-0812340811e45ec4039d409049be53056182a552.tar.xz | |
smb: client: handle max length for SMB symlinks
We can't use PATH_MAX for SMB symlinks because
(1) Windows Server will fail FSCTL_SET_REPARSE_POINT with
STATUS_IO_REPARSE_DATA_INVALID when input buffer is larger than
16K, as specified in MS-FSA 2.1.5.10.37.
(2) The client won't be able to parse large SMB responses that
includes SMB symlink path within SMB2_CREATE or SMB2_IOCTL
responses.
Fix this by defining a maximum length value (4060) for SMB symlinks
that both client and server can handle.
Cc: David Howells <dhowells@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: Paulo Alcantara (Red Hat) <pc@manguebit.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions