From: Kevin Wolf <kwolf@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PULL 01/13] iotests: Set read-zeroes on in null block driver for Valgrind
Date: Wed, 24 Jul 2019 09:38:06 +0200 [thread overview]
Message-ID: <20190724073805.GA4873@localhost.localdomain> (raw)
In-Reply-To: <351d4790-3ea3-9cd2-1c4d-6042ea35507c@virtuozzo.com>
Am 24.07.2019 um 09:30 hat Andrey Shinkevich geschrieben:
>
>
> On 24/07/2019 10:18, Christian Borntraeger wrote:
> >
> > On 19.07.19 15:43, Kevin Wolf wrote:
> >> From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
> >>
> >> The Valgrind tool reports about the uninitialised buffer 'buf'
> >> instantiated on the stack of the function guess_disk_lchs().
> >> Pass 'read-zeroes=on' to the null block driver to make it deterministic.
> >> The output of the tests 051, 186 and 227 now includes the parameter
> >> 'read-zeroes'. So, the benchmark output files are being changed too.
> >>
> >> Suggested-by: Kevin Wolf <kwolf@redhat.com>
> >> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
> >> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> >> ---
> >> tests/qemu-iotests/051 | 10 +--
> >> tests/qemu-iotests/051.pc.out | 10 +--
> >> tests/qemu-iotests/093 | 9 +-
> > [...9
> >
> >
> > I now get the following on s390.
> > Seems that you only fixed 051.pc.out but not 051.out
> >
> > 051 ... [09:01:49] ... 051 ^[[1m^[[31mfail ^[[0m [09:01:49] [09:01:50] output mismatch (see 051.out.bad)
> > --- tests/qemu-iotests/051.out 2019-07-09 18:34:26.734654933 +0200
> > +++ build/tests/qemu-iotests/051.out.bad 2019-07-24 09:01:50.015024901 +0200
> > @@ -149,23 +149,23 @@
> >
> > === Cache modes ===
> >
> > -Testing: -drive driver=null-co,cache=none
> > +Testing: -drive driver=null-co,read-zeroes=on,cache=none
> > QEMU X.Y.Z monitor - type 'help' for more information
> > (qemu) quit
> >
> > -Testing: -drive driver=null-co,cache=directsync
> > +Testing: -drive driver=null-co,read-zeroes=on,cache=directsync
> > QEMU X.Y.Z monitor - type 'help' for more information
> > (qemu) quit
> >
> > -Testing: -drive driver=null-co,cache=writeback
> > +Testing: -drive driver=null-co,read-zeroes=on,cache=writeback
> > QEMU X.Y.Z monitor - type 'help' for more information
> > (qemu) quit
> >
> > -Testing: -drive driver=null-co,cache=writethrough
> > +Testing: -drive driver=null-co,read-zeroes=on,cache=writethrough
> > QEMU X.Y.Z monitor - type 'help' for more information
> > (qemu) quit
> >
> > -Testing: -drive driver=null-co,cache=unsafe
> > +Testing: -drive driver=null-co,read-zeroes=on,cache=unsafe
> > QEMU X.Y.Z monitor - type 'help' for more information
> > (qemu) quit
> >
> >
>
> Thank you Christian for your report.
> Would you please send the command line you ran the 051 test with?
>
> Kevin,
> How do add the 051.out file to the patch? New version?
No, we need a follow-up patch. This one is already merged, so we can't
change it any more.
Kevin
next prev parent reply other threads:[~2019-07-24 7:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 13:43 [Qemu-devel] [PULL 00/13] Block layer patches Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 01/13] iotests: Set read-zeroes on in null block driver for Valgrind Kevin Wolf
2019-07-24 7:18 ` Christian Borntraeger
2019-07-24 7:30 ` Andrey Shinkevich
2019-07-24 7:33 ` Christian Borntraeger
2019-07-24 7:37 ` Andrey Shinkevich
2019-07-24 7:38 ` Kevin Wolf [this message]
2019-07-24 7:57 ` Andrey Shinkevich
2019-07-24 8:05 ` Kevin Wolf
2019-07-24 8:23 ` Andrey Shinkevich
2019-07-19 13:43 ` [Qemu-devel] [PULL 02/13] block: Introduce BdrvChild.parent_quiesce_counter Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 03/13] tests: Add job commit by drained_end test Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 04/13] block: Add @drained_end_counter Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 05/13] block: Make bdrv_parent_drained_[^_]*() static Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 06/13] tests: Lock AioContexts in test-block-iothread Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 07/13] block: Do not poll in bdrv_do_drained_end() Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 08/13] tests: Extend commit by drained_end test Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 09/13] block: Loop unsafely in bdrv*drained_end() Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 10/13] iotests: Add @has_quit to vm.shutdown() Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 11/13] iotests: Test commit with a filter on the chain Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 12/13] vl: Drain before (block) job cancel when quitting Kevin Wolf
2019-07-19 13:43 ` [Qemu-devel] [PULL 13/13] iotests: Test quitting with job on throttled node Kevin Wolf
2019-07-22 9:11 ` [Qemu-devel] [PULL 00/13] Block layer patches Peter Maydell
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=20190724073805.GA4873@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=borntraeger@de.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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).