From: Eric Blake <eblake@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, mreitz@redhat.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
den@openvz.org, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 7/7] block/nbd: NBDReply is used being uninitialized
Date: Fri, 19 Jul 2019 09:34:30 -0500 [thread overview]
Message-ID: <a4214009-e9ba-2f67-138b-30ce31f7905f@redhat.com> (raw)
In-Reply-To: <1563529204-3368-8-git-send-email-andrey.shinkevich@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1426 bytes --]
On 7/19/19 4:40 AM, Andrey Shinkevich wrote:
> In case nbd_co_receive_one_chunk() fails in
> nbd_reply_chunk_iter_receive(), 'NBDReply reply' parameter is used in
> the check nbd_reply_is_simple() without being initialized. The iotest
> 083 does not pass under the Valgrind: $./check -nbd -valgrind 083.
> The alternative solution is to swap the operands in the condition:
> 'if (s->quit || nbd_reply_is_simple(reply))'
>
> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
> ---
> block/nbd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Huh. Very similar to
https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg03712.html, but
affects a different function. I can queue this one through my NBD tree
to get both in my rc2 pull request.
Reviewed-by: Eric Blake <eblake@redhat.com>
>
> diff --git a/block/nbd.c b/block/nbd.c
> index 81edabb..8480ad4 100644
> --- a/block/nbd.c
> +++ b/block/nbd.c
> @@ -786,7 +786,7 @@ static int nbd_co_receive_cmdread_reply(BDRVNBDState *s, uint64_t handle,
> int *request_ret, Error **errp)
> {
> NBDReplyChunkIter iter;
> - NBDReply reply;
> + NBDReply reply = {};
> void *payload = NULL;
> Error *local_err = NULL;
>
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-19 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 9:39 [Qemu-devel] [PATCH v4 0/7] Allow Valgrind checking all QEMU processes Andrey Shinkevich
2019-07-19 9:39 ` [Qemu-devel] [PATCH v4 1/7] iotests: allow " Andrey Shinkevich
2019-07-19 9:39 ` [Qemu-devel] [PATCH v4 2/7] iotests: exclude killed processes from running under Valgrind Andrey Shinkevich
2019-07-19 9:40 ` [Qemu-devel] [PATCH v4 3/7] iotests: Add casenotrun report to bash tests Andrey Shinkevich
2019-07-19 9:40 ` [Qemu-devel] [PATCH v4 4/7] iotests: Valgrind fails with nonexistent directory Andrey Shinkevich
2019-07-19 9:40 ` [Qemu-devel] [PATCH v4 5/7] iotests: extended timeout under Valgrind Andrey Shinkevich
2019-07-19 9:40 ` [Qemu-devel] [PATCH v4 6/7] iotests: extend sleeping time " Andrey Shinkevich
2019-07-19 9:40 ` [Qemu-devel] [PATCH v4 7/7] block/nbd: NBDReply is used being uninitialized Andrey Shinkevich
2019-07-19 14:34 ` Eric Blake [this message]
2019-07-19 14:43 ` Andrey Shinkevich
2019-07-19 14:44 ` Eric Blake
2019-07-19 15:00 ` Andrey Shinkevich
2019-07-19 15:15 ` Eric Blake
2019-07-19 15:43 ` 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=a4214009-e9ba-2f67-138b-30ce31f7905f@redhat.com \
--to=eblake@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@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).