On Fri, May 22, 2020 at 11:35:42AM -0400, Daniele Buono wrote: > On 5/21/2020 5:59 AM, Stefan Hajnoczi wrote: > > On Wed, Apr 29, 2020 at 03:44:20PM -0400, Daniele Buono wrote: > > > > > > > > Signed-off-by: Daniele Buono > > > --- > > > tests/check-block.sh | 12 +++++++++++- > > > 1 file changed, 11 insertions(+), 1 deletion(-) > > > > > > diff --git a/tests/check-block.sh b/tests/check-block.sh > > > index ad320c21ba..8e29c868e5 100755 > > > --- a/tests/check-block.sh > > > +++ b/tests/check-block.sh > > > @@ -21,7 +21,17 @@ if grep -q "CONFIG_GPROF=y" config-host.mak 2>/dev/null ; then > > > exit 0 > > > fi > > > -if grep -q "CFLAGS.*-fsanitize" config-host.mak 2>/dev/null ; then > > > +# Disable tests with any sanitizer except for SafeStack > > > +CFLAGS=$( grep "CFLAGS.*-fsanitize" config-host.mak 2>/dev/null ) > > > +SANITIZE_FLAGS="" > > > +#Remove all occurrencies of -fsanitize=safe-stack > > > +for i in ${CFLAGS}; do > > > + if [ "${i}" != "-fsanitize=safe-stack" ]; then > > > + SANITIZE_FLAGS="${SANITIZE_FLAGS} ${i}" > > > + fi > > > +done > > > +if echo ${SANITIZE_FLAGS} | grep -q "\-fsanitize" 2>/dev/null; then > > > + # Have a sanitize flag that is not allowed, stop > > > echo "Sanitizers are enabled ==> Not running the qemu-iotests." > > > exit 0 > > > fi > > > > The commit that disabled check-block.sh with sanitizers said: > > > > The sanitizers (especially the address sanitizer from Clang) are > > sometimes printing out warnings or false positives - this spoils > > the output of the iotests, causing some of the tests to fail. > > > > It seems fine to allow SafeStack if check-block.sh currently passes with > > it enabled. Does it pass and produce no extra output? > > > Yes, that was the idea. SafeStack should pass the tests without extra > output. > > It did (pass) on my testing machine. However I don't remember if I did the > full (slow) check or only the partial one. > > Will check again before I submit v2 Great, thanks! Stefan