From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.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>
Subject: Re: [Qemu-devel] [PATCH] iotests: Set read-zeroes on in null block driver for Valgrind
Date: Wed, 17 Jul 2019 07:33:58 +0000 [thread overview]
Message-ID: <f21deadb-06cc-a3e1-dd79-02f8f14838ba@virtuozzo.com> (raw)
In-Reply-To: <20190716111928.GA7297@linux.fritz.box>
On 16/07/2019 14:19, Kevin Wolf wrote:
> Am 15.07.2019 um 18:07 hat Andrey Shinkevich geschrieben:
>> 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>
>
> Thanks, applied to the block branch.
>
> Kevin
>
Thank you Kevin!
Andrey
--
With the best regards,
Andrey Shinkevich
next prev parent reply other threads:[~2019-07-17 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 16:07 [Qemu-devel] [PATCH] iotests: Set read-zeroes on in null block driver for Valgrind Andrey Shinkevich
2019-07-16 11:19 ` Kevin Wolf
2019-07-17 7:33 ` Andrey Shinkevich [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-15 16:06 Andrey Shinkevich
2019-07-19 0:14 ` John Snow
2019-07-19 9:23 ` Andrey Shinkevich
2019-07-19 14:15 ` Andrey Shinkevich
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=f21deadb-06cc-a3e1-dd79-02f8f14838ba@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.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).