summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorNamjae Jeon <linkinjeon@kernel.org>2026-08-15 22:17:35 +0900
committerNamjae Jeon <linkinjeon@kernel.org>2026-08-17 22:38:23 +0900
commit68f3508e4c36be026f7526e753a9e1bc3ff6bfbb (patch)
tree836a919c62f9c567fcd9640f05c365eeab3163dd /scripts
parent39f2032096715daae5f6fd0f587ca7a474b019df (diff)
downloadlinux-68f3508e4c36be026f7526e753a9e1bc3ff6bfbb.tar.gz
linux-68f3508e4c36be026f7526e753a9e1bc3ff6bfbb.zip
ksmbd: accept unspecified volatile ID on durable reconnect
BVT_DurableHandleV1_Reconnect_WithBatchOplock, BVT_DurableHandleV1_Reconnect_WithLeaseV1, BVT_DurableHandleV2_Reconnect_WithBatchOplock, and BVT_DurableHandleV2_Reconnect_WithLeaseV1 fail to reconnect a durable handle when the request leaves VolatileFileId unset. A durable reconnect request may omit VolatileFileId by setting it to zero. Treating zero as an ID makes ksmbd reject the request whenever the saved volatile ID is nonzero. Only compare the saved and requested volatile IDs when the request contains a nonzero value. Explicit mismatches continue to be rejected. This allows SMB2 durable handle V1 and V2 reconnects that identify the handle through the persistent ID and reconnect context. Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions