From: "Cédric Le Goater" <clg@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, peter.maydell@linaro.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH for-8.2] test-resv-mem: Fix CID 1523911
Date: Mon, 13 Nov 2023 08:56:03 +0100 [thread overview]
Message-ID: <69f9d31c-893c-492c-aea3-1f0af4f52962@redhat.com> (raw)
In-Reply-To: <b92285b4-156b-4a39-baba-ffc2e80e21bf@redhat.com>
On 11/13/23 08:21, Thomas Huth wrote:
> On 10/11/2023 09.36, Eric Auger wrote:
>> Coverity complains about passing "&expected" to "run_range_inverse_array",
>> which dereferences null "expected". I guess the problem is that the
>> compare_ranges() loop dereferences 'e' without testing it. However the
>> loop condition is based on 'ranges' which is garanteed to have
>> the same length as 'expected' given the g_assert_cmpint() just
>> before the loop. So the code looks safe to me.
>>
>> Nevertheless adding a test on expected before the loop to get rid of the
>> warning.
>>
>> Fixes: CID 1523901
>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>> Reported-by: Coverity (CID 1523901)
>>
>> ---
>>
>> Hope this fixes the Coverity warning as I cannot test.
>> ---
>> tests/unit/test-resv-mem.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/tests/unit/test-resv-mem.c b/tests/unit/test-resv-mem.c
>> index 5963274e2c..cd8f7318cc 100644
>> --- a/tests/unit/test-resv-mem.c
>> +++ b/tests/unit/test-resv-mem.c
>> @@ -44,6 +44,10 @@ static void compare_ranges(const char *prefix, GList *ranges,
>> print_ranges("out", ranges);
>> print_ranges("expected", expected);
>> #endif
>> + if (!expected) {
>> + g_assert_true(!ranges);
>> + return;
>> + }
>> g_assert_cmpint(g_list_length(ranges), ==, g_list_length(expected));
>> for (l = ranges, e = expected; l ; l = l->next, e = e->next) {
>> Range *r = (Range *)l->data;
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
> I'll queue it (unless somebody else wants to take this?).
There is also another fix for the same series :
https://lore.kernel.org/qemu-devel/20231109170715.259520-1-eric.auger@redhat.com/
I was waiting to have a little more for VFIO to queue both but
they could go through your queue also.
Thanks,
C.
next prev parent reply other threads:[~2023-11-13 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 8:36 [PATCH for-8.2] test-resv-mem: Fix CID 1523911 Eric Auger
2023-11-13 7:21 ` Thomas Huth
2023-11-13 7:56 ` Cédric Le Goater [this message]
2023-11-13 7:59 ` Thomas Huth
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=69f9d31c-893c-492c-aea3-1f0af4f52962@redhat.com \
--to=clg@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).