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)
committerRalph Boehme <slow@samba.org>
Thu, 17 Nov 2022 04:58:28 +0000 (04:58 +0000)
commit6f149dfd9d8d2619a9e18975ebcf5e69df2b7766
treed785f631f02cbdc0d726bf7e649210a5bbcdf6d0
parent17a110c1b58196eb8ecf3c76eb97e8508976c544
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>
selftest/knownfail.d/compound_async
source4/torture/smb2/compound.c