From 8ebef3f4c80cbf05dbadf71204c781c28e369ec9 Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Mon, 18 Jul 2005 18:50:13 +0000 Subject: r8545: Fix oplock bug introduced by oplock code "simplification" :-). We *always* reply to an exclusive oplock break message even if we have no record of the oplock (and we always did before 3.0.20pre2). Jeremy. (This used to be commit b1a94aadf25e94dcc168ea3a5ae008f4e84ff296) --- source3/smbd/oplock.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source3/smbd/oplock.c b/source3/smbd/oplock.c index 6ee2454fab..de12003986 100644 --- a/source3/smbd/oplock.c +++ b/source3/smbd/oplock.c @@ -461,12 +461,12 @@ pid %d, port %d, dev = %x, inode = %.0f, file_id = %lu\n", */ DEBUG(3,("process_local_message: oplock break requested with " "no outstanding oplocks. Returning success.\n")); - return True; - } - if (!oplock_break(dev, inode, file_id, False)) { - DEBUG(0,("process_local_message: oplock break failed.\n")); - return False; + } else { + if (!oplock_break(dev, inode, file_id, False)) { + DEBUG(0,("process_local_message: oplock break failed.\n")); + return False; + } } /* -- cgit