From: Stefan Metzmacher Date: Fri, 8 Jun 2012 09:19:00 +0000 (+0200) Subject: s3:smb2_lock: use fsp->fnum as locking context X-Git-Tag: samba-4.0.0beta2~262 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4ae96bb952be47a5043d9906da57a9482e12c21d;p=thirdparty%2Fsamba.git s3:smb2_lock: use fsp->fnum as locking context fsp->fnum is the same as in_file_id_volatile. When we start to support durable handles we should pass in_file_id_persistent. metze --- diff --git a/source3/smbd/smb2_lock.c b/source3/smbd/smb2_lock.c index e4e0cac8b12..c86bcfedd32 100644 --- a/source3/smbd/smb2_lock.c +++ b/source3/smbd/smb2_lock.c @@ -335,7 +335,7 @@ static struct tevent_req *smbd_smb2_lock_send(TALLOC_CTX *mem_ctx, return tevent_req_post(req, ev); } - locks[i].smblctx = in_file_id_volatile; + locks[i].smblctx = fsp->fnum; locks[i].offset = in_locks[i].offset; locks[i].count = in_locks[i].length;