From 4ae96bb952be47a5043d9906da57a9482e12c21d Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Fri, 8 Jun 2012 11:19:00 +0200 Subject: 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 --- source3/smbd/smb2_lock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source3/smbd') diff --git a/source3/smbd/smb2_lock.c b/source3/smbd/smb2_lock.c index e4e0cac8b1..c86bcfedd3 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; -- cgit