From: Roman Kagan <rkagan@virtuozzo.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"berrange@redhat.com" <berrange@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mreitz@redhat.com" <mreitz@redhat.com>,
Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind
Date: Mon, 17 Jun 2019 11:57:18 +0000 [thread overview]
Message-ID: <20190617115715.GA32624@rkaganb.sw.ru> (raw)
In-Reply-To: <3bd93c9c-6f8e-d982-1c60-0cd8b5a9ec51@virtuozzo.com>
On Thu, Jun 13, 2019 at 12:47:21PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 11.06.2019 21:02, Andrey Shinkevich wrote:
> > The Valgrind tool fails to manage its termination when QEMU raises the
> > signal SIGKILL. Lets exclude such test cases from running under the
> > Valgrind because there is no sense to check memory issues that way.
> >
> > Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
> > ---
> > tests/qemu-iotests/039 | 5 +++++
> > tests/qemu-iotests/061 | 2 ++
> > tests/qemu-iotests/137 | 1 +
> > 3 files changed, 8 insertions(+)
> >
> > diff --git a/tests/qemu-iotests/039 b/tests/qemu-iotests/039
> > index 0d4e963..95115e2 100755
> > --- a/tests/qemu-iotests/039
> > +++ b/tests/qemu-iotests/039
> > @@ -65,6 +65,7 @@ echo "== Creating a dirty image file =="
> > IMGOPTS="compat=1.1,lazy_refcounts=on"
> > _make_test_img $size
> >
> > +VALGRIND_QEMU="" \
>
>
> Shouldn't it be written once per test, just without "\" ?
Only qemu-io invocations that perform raise(KILL) need to bypass
valgrinding. Clearing VALGRIND_QEMU globally will indulge all qemu-io
throughout the test.
Roman.
> > $QEMU_IO -c "write -P 0x5a 0 512" \
> > -c "sigraise $(kill -l KILL)" "$TEST_IMG" 2>&1 \
> > | _filter_qemu_io
> > @@ -100,6 +101,7 @@ echo "== Opening a dirty image read/write should repair it =="
> > IMGOPTS="compat=1.1,lazy_refcounts=on"
> > _make_test_img $size
> >
> > +VALGRIND_QEMU="" \
> > $QEMU_IO -c "write -P 0x5a 0 512" \
> > -c "sigraise $(kill -l KILL)" "$TEST_IMG" 2>&1 \
> > | _filter_qemu_io
> > @@ -118,6 +120,7 @@ echo "== Creating an image file with lazy_refcounts=off =="
> > IMGOPTS="compat=1.1,lazy_refcounts=off"
> > _make_test_img $size
> >
> > +VALGRIND_QEMU="" \
> > $QEMU_IO -c "write -P 0x5a 0 512" \
> > -c "sigraise $(kill -l KILL)" "$TEST_IMG" 2>&1 \
> > | _filter_qemu_io
> > @@ -151,6 +154,7 @@ echo "== Changing lazy_refcounts setting at runtime =="
> > IMGOPTS="compat=1.1,lazy_refcounts=off"
> > _make_test_img $size
> >
> > +VALGRIND_QEMU="" \
> > $QEMU_IO -c "reopen -o lazy-refcounts=on" \
> > -c "write -P 0x5a 0 512" \
> > -c "sigraise $(kill -l KILL)" "$TEST_IMG" 2>&1 \
> > @@ -163,6 +167,7 @@ _check_test_img
> > IMGOPTS="compat=1.1,lazy_refcounts=on"
> > _make_test_img $size
> >
> > +VALGRIND_QEMU="" \
> > $QEMU_IO -c "reopen -o lazy-refcounts=off" \
> > -c "write -P 0x5a 0 512" \
> > -c "sigraise $(kill -l KILL)" "$TEST_IMG" 2>&1 \
> > diff --git a/tests/qemu-iotests/061 b/tests/qemu-iotests/061
> > index d7dbd7e..5d0724c 100755
> > --- a/tests/qemu-iotests/061
> > +++ b/tests/qemu-iotests/061
> > @@ -73,6 +73,7 @@ echo
> > echo "=== Testing dirty version downgrade ==="
> > echo
> > IMGOPTS="compat=1.1,lazy_refcounts=on" _make_test_img 64M
> > +VALGRIND_QEMU="" \
> > $QEMU_IO -c "write -P 0x2a 0 128k" -c flush \
> > -c "sigraise $(kill -l KILL)" "$TEST_IMG" 2>&1 | _filter_qemu_io
> > $PYTHON qcow2.py "$TEST_IMG" dump-header
> > @@ -107,6 +108,7 @@ echo
> > echo "=== Testing dirty lazy_refcounts=off ==="
> > echo
> > IMGOPTS="compat=1.1,lazy_refcounts=on" _make_test_img 64M
> > +VALGRIND_QEMU="" \
> > $QEMU_IO -c "write -P 0x2a 0 128k" -c flush \
> > -c "sigraise $(kill -l KILL)" "$TEST_IMG" 2>&1 | _filter_qemu_io
> > $PYTHON qcow2.py "$TEST_IMG" dump-header
> > diff --git a/tests/qemu-iotests/137 b/tests/qemu-iotests/137
> > index 0c3d2a1..a442fc8 100755
> > --- a/tests/qemu-iotests/137
> > +++ b/tests/qemu-iotests/137
> > @@ -130,6 +130,7 @@ echo
> >
> > # Whether lazy-refcounts was actually enabled can easily be tested: Check if
> > # the dirty bit is set after a crash
> > +VALGRIND_QEMU="" \
> > $QEMU_IO \
> > -c "reopen -o lazy-refcounts=on,overlap-check=blubb" \
> > -c "write -P 0x5a 0 512" \
> >
>
>
> --
> Best regards,
> Vladimir
next prev parent reply other threads:[~2019-06-17 12:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:02 [Qemu-devel] [PATCH v2 0/7] Allow Valgrind checking all QEMU processes Andrey Shinkevich
2019-06-11 18:02 ` [Qemu-devel] [PATCH v2 1/7] iotests: allow " Andrey Shinkevich
2019-06-13 9:44 ` Vladimir Sementsov-Ogievskiy
2019-06-27 15:08 ` Andrey Shinkevich
2019-06-13 9:45 ` Vladimir Sementsov-Ogievskiy
2019-06-11 18:02 ` [Qemu-devel] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind Andrey Shinkevich
2019-06-13 9:47 ` Vladimir Sementsov-Ogievskiy
2019-06-17 11:57 ` Roman Kagan [this message]
2019-06-17 11:15 ` Kevin Wolf
2019-06-17 12:18 ` Roman Kagan
2019-06-17 12:53 ` Kevin Wolf
2019-06-17 13:20 ` Roman Kagan
2019-06-17 14:51 ` Kevin Wolf
2019-06-24 16:55 ` Andrey Shinkevich
2019-06-11 18:02 ` [Qemu-devel] [PATCH v2 3/7] iotests: Valgrind fails to work with nonexistent directory Andrey Shinkevich
2019-06-13 9:52 ` Vladimir Sementsov-Ogievskiy
2019-06-17 11:22 ` Kevin Wolf
2019-06-11 18:02 ` [Qemu-devel] [PATCH v2 4/7] iotests: extended timeout under Valgrind Andrey Shinkevich
2019-06-13 9:54 ` Vladimir Sementsov-Ogievskiy
2019-06-11 18:02 ` [Qemu-devel] [PATCH v2 5/7] iotests: extend sleeping time " Andrey Shinkevich
2019-06-13 9:55 ` Vladimir Sementsov-Ogievskiy
2019-06-11 18:02 ` [Qemu-devel] [PATCH v2 6/7] iotests: amend QEMU NBD process synchronization Andrey Shinkevich
2019-06-13 9:59 ` Vladimir Sementsov-Ogievskiy
2019-06-17 12:45 ` Roman Kagan
2019-06-17 12:38 ` Roman Kagan
2019-06-11 18:02 ` [Qemu-devel] [PATCH v2 7/7] iotests: new file to suppress Valgrind errors Andrey Shinkevich
2019-06-13 10:06 ` Vladimir Sementsov-Ogievskiy
2019-06-24 16:55 ` Andrey Shinkevich
2019-06-24 17:09 ` Eric Blake
2019-06-24 17:23 ` Andrey Shinkevich
2019-06-17 11:45 ` Kevin Wolf
2019-06-24 16:55 ` Andrey Shinkevich
2019-06-25 8:13 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617115715.GA32624@rkaganb.sw.ru \
--to=rkagan@virtuozzo.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=berrange@redhat.com \
--cc=den@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).