From de870e979b1082ffd4d88350dfd4e073bd5d0789 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Tue, 28 Feb 2012 02:47:46 +0100 Subject: s3: Introduce "req" helper var in reply_lockingX_success Autobuild-User: Volker Lendecke Autobuild-Date: Wed Feb 29 03:08:53 CET 2012 on sn-devel-104 --- source3/smbd/blocking.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source3/smbd/blocking.c b/source3/smbd/blocking.c index 028adce71c..6496e43505 100644 --- a/source3/smbd/blocking.c +++ b/source3/smbd/blocking.c @@ -268,7 +268,9 @@ bool push_blocking_lock_request( struct byte_range_lock *br_lck, static void reply_lockingX_success(struct blocking_lock_record *blr) { - reply_outbuf(blr->req, 2, 0); + struct smb_request *req = blr->req; + + reply_outbuf(req, 2, 0); /* * As this message is a lockingX call we must handle @@ -278,8 +280,8 @@ static void reply_lockingX_success(struct blocking_lock_record *blr) * that here and must set up the chain info manually. */ - chain_reply(blr->req); - TALLOC_FREE(blr->req->outbuf); + chain_reply(req); + TALLOC_FREE(req->outbuf); } /**************************************************************************** -- cgit