s3:torture: fix the timeout alarm handling on LOCK9

smbXcli_conn_disconnect(alarm_cli->conn, NT_STATUS_OK)
means existing requests are not finished with an error,
but instead just keep dangling arround.

Pass NT_STATUS_LOCAL_DISCONNECT in order to fail the
cli_lock32() call after getting SIGALARM.

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>

diff --git a/source3/torture/torture.c b/source3/torture/torture.c
index 7ead71c644db4a15f26d0f3c4a66ecf60e585004..9d214f55973f122978d84e67cd189fda1ab2f204 100644 (file)
--- a/source3/torture/torture.c
+++ b/source3/torture/torture.c
@@ -2544,7 +2544,7 @@ static void alarm_handler(int dummy)
 
 static void alarm_handler_parent(int dummy)
 {
-       smbXcli_conn_disconnect(alarm_cli->conn, NT_STATUS_OK);
+       smbXcli_conn_disconnect(alarm_cli->conn, NT_STATUS_LOCAL_DISCONNECT);
 }
 
 static void do_local_lock(int read_fd, int write_fd)