From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
Roman Kagan <rkagan@virtuozzo.com>,
"berrange@redhat.com" <berrange@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"mreitz@redhat.com" <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 7/7] iotests: new file to suppress Valgrind errors
Date: Mon, 24 Jun 2019 16:55:50 +0000 [thread overview]
Message-ID: <5b57cb61-7eef-b89e-7ea7-053e65c9f227@virtuozzo.com> (raw)
In-Reply-To: <dc4ae7d2-64bf-ab12-4712-5752f848b5dd@virtuozzo.com>
On 13/06/2019 13:06, Vladimir Sementsov-Ogievskiy wrote:
> 11.06.2019 21:02, Andrey Shinkevich wrote:
>> The Valgrind tool reports about an uninitialised memory usage when the
>> initialization is actually not needed. For example, the buffer 'buf'
>> instantiated on a stack of the function guess_disk_lchs().
>
> for convinience, you may add: "of the function guess_disk_lchs(), which
> is then actually initialized by blk_pread_unthrottled()"
>
>> Let's use the Valgrind technology to suppress the unwanted reports by
>> adding the Valgrind specific format file valgrind.supp to the QEMU
>> project. The file content is extendable for future needs.
>>
>> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
>> ---
>> tests/qemu-iotests/common.rc | 5 ++++-
>> tests/qemu-iotests/valgrind.supp | 31 +++++++++++++++++++++++++++++++
>> 2 files changed, 35 insertions(+), 1 deletion(-)
>> create mode 100644 tests/qemu-iotests/valgrind.supp
>>
>> diff --git a/tests/qemu-iotests/common.rc b/tests/qemu-iotests/common.rc
>> index 3caaca4..9b74890 100644
>> --- a/tests/qemu-iotests/common.rc
>> +++ b/tests/qemu-iotests/common.rc
>> @@ -17,6 +17,8 @@
>> # along with this program. If not, see <http://www.gnu.org/licenses/>.
>> #
>>
>> +readonly VALGRIND_SUPPRESS_ERRORS=./valgrind.supp
>
> Why readonly?
>
> I think it should be defined near and in same manner as VALGRIND_LOGFILE,
> with use of TEST_DIR
>
The new file 'valgrind.supp' is intended to be a part of the QEMU
project. So, it will be located in the test directory tests/qemu-iotests.
The variable TEST_DIR may change the working directory. In that case,
moving the project file will be a hassle.
Andrey
>> +
>> SED=
>> for sed in sed gsed; do
>> ($sed --version | grep 'GNU sed') > /dev/null 2>&1
>> @@ -65,7 +67,8 @@ _qemu_proc_wrapper()
>> local VALGRIND_LOGFILE="$1"
>> shift
>> if [ "${VALGRIND_QEMU}" == "y" ]; then
>> - exec valgrind --log-file="${VALGRIND_LOGFILE}" --error-exitcode=99 "$@"
>> + exec valgrind --log-file="${VALGRIND_LOGFILE}" --error-exitcode=99 \
>> + --suppressions="${VALGRIND_SUPPRESS_ERRORS}" "$@"
>> else
>> exec "$@"
>> fi
>> diff --git a/tests/qemu-iotests/valgrind.supp b/tests/qemu-iotests/valgrind.supp
>> new file mode 100644
>> index 0000000..78215b6
>> --- /dev/null
>> +++ b/tests/qemu-iotests/valgrind.supp
>> @@ -0,0 +1,31 @@
>> +#
>> +# Valgrind errors suppression file for QEMU iotests
>> +#
>> +# Copyright (c) 2019 Virtuozzo International GmbH
>> +#
>> +# This program is free software; you can redistribute it and/or modify
>> +# it under the terms of the GNU General Public License as published by
>> +# the Free Software Foundation; either version 2 of the License, or
>> +# (at your option) any later version.
>> +#
>> +# This program is distributed in the hope that it will be useful,
>> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
>> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>> +# GNU General Public License for more details.
>> +#
>> +# You should have received a copy of the GNU General Public License
>> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
>> +#
>> +{
>> + hw/block/hd-geometry.c
>> + Memcheck:Cond
>> + fun:guess_disk_lchs
>> + fun:hd_geometry_guess
>> + fun:blkconf_geometry
>> + ...
>> + fun:device_set_realized
>> + fun:property_set_bool
>> + fun:object_property_set
>> + fun:object_property_set_qobject
>> + fun:object_property_set_bool
>> +}
>>
>
>
--
With the best regards,
Andrey Shinkevich
next prev parent reply other threads:[~2019-06-24 17:00 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
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 [this message]
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=5b57cb61-7eef-b89e-7ea7-053e65c9f227@virtuozzo.com \
--to=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=rkagan@virtuozzo.com \
--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).