From 90b33a05e967e9e29c4584bed188ef6fa5a3fbf0 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Sun, 26 Feb 2012 16:49:09 +0100 Subject: s3: Make sure the andX chains are ended correctly Normally chain_reply took care of this. This will go away soon. --- source3/smbd/blocking.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'source3/smbd/blocking.c') diff --git a/source3/smbd/blocking.c b/source3/smbd/blocking.c index 6496e43505..ac878926d1 100644 --- a/source3/smbd/blocking.c +++ b/source3/smbd/blocking.c @@ -271,6 +271,8 @@ static void reply_lockingX_success(struct blocking_lock_record *blr) struct smb_request *req = blr->req; reply_outbuf(req, 2, 0); + SSVAL(req->outbuf, smb_vwv0, 0xff); /* andx chain ends */ + SSVAL(req->outbuf, smb_vwv1, 0); /* no andx offset */ /* * As this message is a lockingX call we must handle -- cgit