s4: torture: Add an async SMB2_OP_FLUSH + SMB2_OP_FLUSH test to smb2.compound_async.
authorJeremy Allison <jra@samba.org>
Thu, 20 Oct 2022 21:22:25 +0000 (14:22 -0700)
committerJule Anger <janger@samba.org>
Mon, 16 Jan 2023 09:40:17 +0000 (09:40 +0000)
commit9b357c947fd6c36779f49dc37f9c81392c9c81fb
treeba76b1d8d62e5311afa371b753c265bb15090518
parentc9ed55b39efc7638b898db6df8352b10950c6c93
s4: torture: Add an async SMB2_OP_FLUSH + SMB2_OP_FLUSH test to smb2.compound_async.

Shows we fail sending an SMB2_OP_FLUSH + SMB2_OP_FLUSH
compound if we immediately close the file afterward.

Internally the flushes go async and we free the req, then
we process the close. When the flushes complete they try to access
already freed data.

Extra test which will allow me to test when the final
component (flush) of the compound goes async and returns
NT_STATUS_PENDING.

Add knownfail.

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

Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Ralph Boehme <slow@samba.org>
(cherry picked from commit 6f149dfd9d8d2619a9e18975ebcf5e69df2b7766)
selftest/knownfail.d/compound_async
source4/torture/smb2/compound.c