From: Paolo Bonzini <pbonzini@redhat.com>
To: Patrick Venture <venture@google.com>,
peter.maydell@linaro.org, armbru@redhat.com
Cc: qemu-devel@nongnu.org, Peter Foley <pefoley@google.com>
Subject: Re: [PATCH] util/keyval: fix msan findings
Date: Sat, 1 Mar 2025 07:12:29 +0100 [thread overview]
Message-ID: <fc1f2750-f4c7-419f-b667-301fb0bb2edf@redhat.com> (raw)
In-Reply-To: <20250228212039.1768614-1-venture@google.com>
On 2/28/25 22:20, Patrick Venture wrote:
> From: Peter Foley <pefoley@google.com>
>
> e.g.
> qemu: Uninitialized value was created by an allocation of 'key_in_cur.i' in the stack frame
> qemu: #0 0xaaaac49f489c in keyval_parse_one third_party/qemu/util/keyval.c:190:5
>
> Signed-off-by: Peter Foley <pefoley@google.com>
> Signed-off-by: Patrick Venture <venture@google.com>
This is not a fix, since there's no bug to fix. It's just the tool
complaining about something it can't reason on.
Paolo
> ---
> util/keyval.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/util/keyval.c b/util/keyval.c
> index a70629a481..f33c64079d 100644
> --- a/util/keyval.c
> +++ b/util/keyval.c
> @@ -187,7 +187,7 @@ static const char *keyval_parse_one(QDict *qdict, const char *params,
> {
> const char *key, *key_end, *val_end, *s, *end;
> size_t len;
> - char key_in_cur[128];
> + char key_in_cur[128] = {};
> QDict *cur;
> int ret;
> QObject *next;
next prev parent reply other threads:[~2025-03-01 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 21:20 [PATCH] util/keyval: fix msan findings Patrick Venture
2025-03-01 6:12 ` Paolo Bonzini [this message]
2025-03-01 7:14 ` Markus Armbruster
2025-03-03 16:32 ` Peter Foley
2025-03-03 18:51 ` Paolo Bonzini
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=fc1f2750-f4c7-419f-b667-301fb0bb2edf@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=pefoley@google.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=venture@google.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).