OS/2 and chained commands

Volker Lendecke Volker.Lendecke at SerNet.DE
Wed Feb 5 07:43:21 MST 2014

On Tue, Feb 04, 2014 at 10:36:58AM -0600, Steve French wrote:
> In testing OS/2 against Samba, I noticed only minor problems so far
> (bcc padding issues on a few commands that the client ignores), but I
> had heard that there was an issue with SMB_COM_WRITE_AND_X (chained
> with unlock or close?) but haven't been able to find any report of
> this - and given the activity testing OS/2 around release 3.0.20 would
> think that it would have been noticed.   Anyone aware of any OS/2
> interoperability issues with Samba?
> In traces of file copy, I do see smb opcode 0x2C (SMB_WRITE_AND_CLOSE)
> which is not really a chained operation.  In traces of the 'e' editor
> I see write requests but not chained write requests
> Any idea if Samba has problems with any chained requests - I haven't
> found any evidence so far - or ideas how to reproduce this
> write/unlock?

We're not talking about write and close. We're talking about
write&x and a close.

There's certainly


which is fixed. In that area we have seen the write&x data
buffer behind the close 16-bit area, which Samba does not
use. Mabye you want to dig up your OS/2 redirector sources
to see how you can trigger write&x and close?


SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de

More information about the samba-technical mailing list