Re: [PATCH 0/7] ksmbd: assorted fixes found while adding macOS/Time Machine support

On Tue, Jul 7, 2026 at 7:01 PM Gaël Blivet-Bailly <[email protected]> wrote:
>
> From: Gael Blivet <[email protected]>
>
> These 7 fixes are independent of each other and of any Apple-specific
> behavior -- they affect any SMB2/SMB3 client. Found while developing
> and live-testing macOS Time Machine support against ksmbd (that series
> is being sent separately, based on the same tree).
>
> Two are worth flagging specifically:
>
> - "fix COPYCHUNK for ADS streams" and "report actual xattr value length
>   for stream EndOfFile/AllocationSize" affect any client using alternate
>   data streams, not just macOS.
>
> - "fix off-by-one rejecting minimal COPYCHUNK query-limits request"
>   affects any client probing server copy limits with a minimal
>   FSCTL_SRV_COPYCHUNK request (ChunkCount=0).
>
> Each commit builds standalone against ksmbd-for-next-next and has been
> checked with checkpatch.pl --strict. The underlying bugs and fixes
> were found and verified during live Time Machine/Finder testing on an
> earlier baseline; this re-derivation against ksmbd-for-next-next has
> been verified to build cleanly but not independently re-tested at
> runtime.
>
> Gael Blivet (7):
>   ksmbd: fix off-by-one rejecting minimal COPYCHUNK query-limits request
>   ksmbd: route stream FileDispositionInformation through stream delete
>     flag
>   ksmbd: report actual xattr value length for stream
>     EndOfFile/AllocationSize
>   ksmbd: return STATUS_OBJECT_NAME_NOT_FOUND for unknown IPC pipe names
>   ksmbd: quiet mdssvc RPC log spam
>   ksmbd: fix stale sparse-file attribute after share reconfiguration
>   ksmbd: fix COPYCHUNK for ADS streams
Applied them to #ksmbd-for-next-next except 0007 patch.

I have applied the following patches instead of 0007 patch.
https://github.com/smfrench/smb3-kernel/commit/165e5b86fd2c5894c9d81ebb3dc898a82e55c440
https://github.com/smfrench/smb3-kernel/commit/8afe741dbd67df46274434a83de767f6dc3ef247

Thanks.