ksmbd_compress_response(9)
β¨ NAME β¨
Okay bestie, meet ksmbd_compress_response(9) from the Kernel API Manual β the function that compresses an eligible ksmbd response. π
πΈ SYNOPSIS πΈ
int ksmbd_compress_response (struct ksmbd_work *work );
π ARGUMENTS π
workβ the request work item containing the response iov.
π¦ DESCRIPTION π¦
So hereβs the vibe: compression transforms describe one contiguous SMB2 message, while ksmbd builds responses from multiple iov entries. π«Ά
The move is: flatten the response first, produce the negotiated transform, and replace the response iov only when the result is smaller than the original message. No cap, size matters here. β¨
Encrypted and compound responses are intentionally left unchanged β like, not me touching those, theyβre giving βdo not disturb.β π
The caller may still continue sending the original response when this function returns zero. So zero is not a fail, itβs just βwe skipped compression, keep it moving.β π
π₯ RETURN π₯
1β the response was replaced. Slay. π0β compression was skipped. Still valid, bestie. π- a negative errno β failure. π
π SEE ALSO π
- Kernel file:
./fs/smb/server/compress.c ksmbd_decompress_request(9)ksmbd_decompress_work_request(9)
Source/version: ./fs/smb/server Β· Date: October 2026 Β· Page: ksmbd_compress_response(9) β bye bestie, go compress responsibly! πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms