These tests leak resources, sometimes in the good path, sometimes
in the fail path. To satisfy LeakSanitizer, clean them up.

Signed-off-by: Michael de Lang <[email protected]>

These tests use some form of dereferencing custom pointers or force usage
after free, tripping up the address sanitizer.

Signed-off-by: Michael de Lang <[email protected]>

Signed-off-by: Michael de Lang <[email protected]>

If the user provides a malloc()'d piece of memory, munmap will not be able
to unmap it, leaking a resource.

Signed-off-by: Michael de Lang <[email protected]>

This change introduces support for using the address sanitizer
checking the opague, user-provided pointers as well as various
pointers provided through functions.
It does this by looping over the sqe's in userspace in
`__io_uring_submit`, check their opcodes and use the sanitizer
interface to check for memory poison values.

Enabled through using the --enable-sanitizer flag when calling configure.

Signed-off-by: Michael de Lang <[email protected]>

This requires adding an "expected fail" mode to runtests.sh.
The tests use obvious bugs, like use after free, to force asan to report
an error and kill the test, exiting with error code 1.

Signed-off-by: Michael de Lang <[email protected]>

Signed-off-by: Michael de Lang <[email protected]>