Created attachment 18901 [details] Capture of the Samba response. While we were testing with files with a large number of streams (5,000 on Windows Server 2019 and 10,000 with Samba) we found a difference between Samba's behavior and the behavior of Windows. Both Samba and Windows return STATUS_BUFFER_OVERFLOW but Windows returns as many stream structs as will fit in the buffer supplied, while Samba returns zero entries. Further, Samba sets the OutPutBufferOffset field to 0. The spec is ambiguous in regard to the value of the OutputBufferOffset, however, it seems Samba should do what Windows does. https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/3b1b3598-a898-44ca-bfac-2dcae065247f Attached are two captures, one against Windows Server 2019 and one against Samba (derived from 4.7.1).
Created attachment 18902 [details] Capture of the Windows behavior.
Sorry. Added (incorrect) comment to the wrong bug. Please ignore.