s4/torture: fix small bug in lock test

Cleanup path should unlock, not cancel existing locked range.

diff --git a/source4/torture/raw/lock.c b/source4/torture/raw/lock.c
index 0af73e503a637b276be95e15726a7c87f126f32c..7eb461048befa0caa92e3557ae2d0cde678cc049 100644 (file)
--- a/source4/torture/raw/lock.c
+++ b/source4/torture/raw/lock.c
@@ -643,6 +643,7 @@ static bool test_async(struct torture_context *tctx,
        /* cleanup the second lock */
        io.lockx.in.ulock_cnt = 1;
        io.lockx.in.lock_cnt = 0;
        /* cleanup the second lock */
        io.lockx.in.ulock_cnt = 1;
        io.lockx.in.lock_cnt = 0;

+       io.lockx.in.mode = LOCKING_ANDX_LARGE_FILES;

        io.lockx.in.locks = &lock[1];
        status = smb_raw_lock(cli->tree, &io);
        CHECK_STATUS(status, NT_STATUS_OK);
        io.lockx.in.locks = &lock[1];
        status = smb_raw_lock(cli->tree, &io);
        CHECK_STATUS(status, NT_STATUS_OK);