sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
Code

s4:torture/raw: assert to get LOCK_NOT_GRANTED in torture_samba3_posixtimedlock()

Browse Source 
There should not be a different if the blocker is a posix process
instead of another smbd.

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

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Volker Lendecke <vl@samba.org>
This commit is contained in:
Stefan Metzmacher 2019-08-19 16:30:16 +02:00
parent 15765644d2
commit 2a77025a1e
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
selftest/knownfail.d/samba3posixtimedlock Normal file
View File

@ -0,0 +1 @@
^samba3.raw.samba3posixtimedlock.samba3posixtimedlock

6
source4/torture/raw/samba3misc.c
View File

@ -775,8 +775,8 @@ static void receive_lock_result(struct smbcli_request *req)
}
/*
* Check that Samba3 correctly deals with conflicting posix byte range locks
* on an underlying file
* Check that Samba3 correctly deals with conflicting local posix byte range
* locks on an underlying file via "normal" SMB1 (without unix extentions).
*
* Note: This test depends on "posix locking = yes".
* Note: To run this test, use "--option=torture:localdir=<LOCALDIR>"
@ -873,7 +873,7 @@ bool torture_samba3_posixtimedlock(struct torture_context *tctx, struct smbcli_s
status = smb_raw_lock(cli->tree, &io);
ret = true;
CHECK_STATUS(tctx, status, NT_STATUS_FILE_LOCK_CONFLICT);
CHECK_STATUS(tctx, status, NT_STATUS_LOCK_NOT_GRANTED);
if (!ret) {
goto done;