[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cifs-protocol
Subject:    Re: [cifs-protocol] Handling of STATUS_BUFFER_OVERFLOW on
From:       Bill Wesse <billwe () microsoft ! com>
Date:       2010-04-28 14:42:31
Message-ID: 38B58112393ABF47AA9F6B99206881E1451448E1 () TK5EX14MBXC133 ! redmond ! corp ! microsoft ! com
[Download RAW message or body]

Hello Stefan; thank you for your questions regarding the [MS-SMB] protocol \
specification. One of my colleagues will be in touch with you shortly, and will \
provide the service request name and number.

Regards,
Bill Wesse
MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
Email:   billwe@microsoft.com
Tel:       +1(980) 776-8200
Cell:      +1(704) 661-5438
Fax:      +1(704) 665-9606


-----Original Message-----
From: Stefan (metze) Metzmacher [mailto:metze@samba.org] 
Sent: Wednesday, April 28, 2010 8:32 AM
To: Interoperability Documentation Help
Cc: pfif@tridgell.net; cifs-protocol@samba.org
Subject: Handling of STATUS_BUFFER_OVERFLOW on SMB_COM_READ_ANDX

Hi,

I need some help regarding the interaction of STATUS_BUFFER_OVERFLOW and chained SMB \
requests.

For SMB_COM_READ_ANDX requests on named pipes it can happen that the server has to \
return STATUS_BUFFER_OVERFLOW (see MS-CIFS 3.3.5.35 Receiving an SMB_COM_READ_ANDX \
Request).

Are chained requests possible in this case?

As there's only one status field for all requests in the chain, it's not clear how a \
server should handle such a situation.

metze

_______________________________________________
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol


[prev in list] [next in list] [prev in thread] [next in thread]