From: Peter Maydell <peter.maydell@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Alexandre Iooss" <erdnaxe@crans.org>,
"Mahmoud Mandour" <ma.mandourr@gmail.com>
Subject: Re: [PATCH] contrib/plugins/execlog: Explicitly check for qemu_plugin_read_register() failure
Date: Mon, 1 Sep 2025 17:19:23 +0100 [thread overview]
Message-ID: <CAFEAcA8Dz5eic1MfKYjQjtMXzjrM50DmGefABYjKNendicHOSw@mail.gmail.com> (raw)
In-Reply-To: <f6c75047-d074-4200-a33a-c864e7beadf1@linaro.org>
Hi Alex -- this patch was reviewed back in July but didn't
make it into git before 10.1 freeze; would you like to
pick it up now we've reopened for 10.2 ?
thanks
-- PMM
On Thu, 10 Jul 2025 at 16:21, Pierrick Bouvier
<pierrick.bouvier@linaro.org> wrote:
>
> On 7/10/25 7:45 AM, Peter Maydell wrote:
> > In insn_check_regs() we don't explicitly check whether
> > qemu_plugin_read_register() failed, which confuses Coverity into
> > thinking that sz can be -1 in the memcmp(). In fact the assertion
> > that sz == reg->last->len means this can't happen, but it's clearer
> > to both humans and Coverity if we explicitly assert that sz > 0, as
> > we already do in init_vcpu_register().
> >
> > Coverity: CID 1611901, 1611902
> > Fixes: af6e4e0a22c1 ("contrib/plugins: extend execlog to track register changes")
> > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> > ---
> > contrib/plugins/execlog.c | 1 +
> > 1 file changed, 1 insertion(+)
>
> Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
next prev parent reply other threads:[~2025-09-01 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 14:45 [PATCH] contrib/plugins/execlog: Explicitly check for qemu_plugin_read_register() failure Peter Maydell
2025-07-10 15:21 ` Pierrick Bouvier
2025-09-01 16:19 ` Peter Maydell [this message]
2025-09-01 17:09 ` Alex Bennée
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=CAFEAcA8Dz5eic1MfKYjQjtMXzjrM50DmGefABYjKNendicHOSw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=erdnaxe@crans.org \
--cc=ma.mandourr@gmail.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@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).