s3: SMB2 : Fix leak of blocking lock records in the database.
commit690012edb6cd0098ae76ddf461dce3c85731ff09
authorJeremy Allison <jra@samba.org>
Thu, 26 Jun 2014 19:08:46 +0000 (26 12:08 -0700)
committerKarolin Seeger <kseeger@samba.org>
Thu, 17 Jul 2014 18:59:16 +0000 (17 20:59 +0200)
treeab687f3f8fb756319fc8758bbe383cf4441dd177
parent0a7cda5e8c3698d348d30571f590d2fb039b16fe
s3: SMB2 : Fix leak of blocking lock records in the database.

Based on a fix from Hemanth Thummala <hemanth.thummala@gmail.com>
Bug #10673 - Increasing response times for byte range unlock requests.

The previous refactoring makes it obvious we need to call
remove_pending_lock() in all places where we are returning
from the SMB2 blocking lock call.

https://bugzilla.samba.org/show_bug.cgi?id=10673

Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Ira Cooper <ira@samba.org>
Reviewed-by: Volker Lendecke <vl@samba.org>
Autobuild-User(master): Volker Lendecke <vl@samba.org>
Autobuild-Date(master): Mon Jun 30 14:59:16 CEST 2014 on sn-devel-104

(cherry picked from commit cee1531e551e5ccd5ccd4a55de226ad686919486)
source3/smbd/smb2_lock.c