s4: torture: Add an async SMB2_OP_FLUSH + SMB2_OP_CLOSE test to smb2.compound_async.
authorJeremy Allison <jra@samba.org>
Tue, 18 Oct 2022 23:22:33 +0000 (16:22 -0700)
committerRalph Boehme <slow@samba.org>
Thu, 17 Nov 2022 04:58:28 +0000 (04:58 +0000)
commit17a110c1b58196eb8ecf3c76eb97e8508976c544
tree93c809fc58300747851b2cf2b4613e4e92125b3b
parentf6284877ce07fc5ddf4f4e2d824013b645d6e12c
s4: torture: Add an async SMB2_OP_FLUSH + SMB2_OP_CLOSE test to smb2.compound_async.

Shows we fail sending an SMB2_OP_FLUSH + SMB2_OP_CLOSE
compound. Internally the flush goes async and
we free the req, then we process the close.
When the flush completes it tries to access
already freed data.

Found using the Apple MacOSX client at SNIA SDC 2022.

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 [new file with mode: 0644]
source3/selftest/tests.py
source4/torture/smb2/compound.c
source4/torture/smb2/smb2.c