From: Liam Merwick <liam.merwick@oracle.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, jsnow@redhat.com,
berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 6/8] block: dump_qlist() may dereference a Null pointer
Date: Mon, 5 Nov 2018 21:38:20 +0000 [thread overview]
Message-ID: <858844d0-9e9d-d25f-b105-d8ddf2a58ab7@oracle.com> (raw)
In-Reply-To: <3037dd84-e7b9-b786-4594-107ae737af2c@redhat.com>
On 05/11/18 00:07, Max Reitz wrote:
> On 19.10.18 22:39, Liam Merwick wrote:
>> A NULL 'list' passed into function dump_qlist() isn't correctly
>> validated and can be passed to qlist_first() where it is dereferenced.
>>
>> Given that dump_qlist() is static, and callers already do the right
>> thing, just add an assert to catch future potential bugs (plus the
>> added benefit of suppressing a warning from a static analysis tool
>> and removing this noise will help us better find real issues).
>
> But can't you fix the tool?
I don't have access to the tool source but have been filing bugs against
it as I run it on the QEMU codebase and discover false positives.
> My opinion is still that large parts of our
> code do not assert that some parameter is not NULL, and I think it isn't
> a good idea to make them assert that.
Yeah, that can be a slippery slope....
> I don't know what makes this
> function special, and I wonder why it is special to your tool -- as I've
> said in the last version, dump_qdict() is basically the same in this
> regard. I wonder why your tool doesn't mind that.
>
I had gone though the code paths to try to see how the tool was happy
with one and not the other - the implementation differed slightly w.r.t
macro usage but I couldn't see any obvious reason.
> Can you not whitelist something as false positives? I know we have a
> lot of those in Coverity, and we just mark them as such, and that's it.
Yeah, I can flag this as a FP and have it fall off my list.
I'll will drop this patch in v5
Regards,
Liam
>
> Finally, one could argue that the nonnull GCC function attribute would
> be a better fit, actually.
>
> But overall, I just don't think it's a good idea to start changing the
> code to accommodate for false positives in static analyzers, because in
> my experience the number of false positives only rises with time.
>
> Max
>
>> Signed-off-by: Liam Merwick <Liam.Merwick@oracle.com>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>> ---
>> block/qapi.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/block/qapi.c b/block/qapi.c
>> index c66f949db839..e81be604217c 100644
>> --- a/block/qapi.c
>> +++ b/block/qapi.c
>> @@ -740,6 +740,8 @@ static void dump_qlist(fprintf_function func_fprintf, void *f, int indentation,
>> const QListEntry *entry;
>> int i = 0;
>>
>> + assert(list);
>> +
>> for (entry = qlist_first(list); entry; entry = qlist_next(entry), i++) {
>> QType type = qobject_type(entry->value);
>> bool composite = (type == QTYPE_QDICT || type == QTYPE_QLIST);
>>
>
>
next prev parent reply other threads:[~2018-11-05 21:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 20:38 [Qemu-devel] [PATCH v4 0/8] off-by-one and NULL pointer accesses detected by static analysis Liam Merwick
2018-10-19 20:38 ` [Qemu-devel] [PATCH v4 1/8] configure: Provide option to explicitly disable AVX2 Liam Merwick
2018-10-19 20:39 ` [Qemu-devel] [PATCH v4 2/8] job: Fix off-by-one assert checks for JobSTT and JobVerbTable Liam Merwick
2018-10-19 20:39 ` [Qemu-devel] [PATCH v4 3/8] block: Null pointer dereference in blk_root_get_parent_desc() Liam Merwick
2018-11-04 23:57 ` Max Reitz
2018-11-05 21:38 ` Liam Merwick
2018-10-19 20:39 ` [Qemu-devel] [PATCH v4 4/8] qemu-img: assert block_job_get() does not return NULL in img_commit() Liam Merwick
2018-11-04 23:59 ` Max Reitz
2018-10-19 20:39 ` [Qemu-devel] [PATCH v4 5/8] block: Fix potential Null pointer dereferences in vvfat.c Liam Merwick
2018-11-05 0:19 ` Max Reitz
2018-11-05 21:38 ` Liam Merwick
2018-10-19 20:39 ` [Qemu-devel] [PATCH v4 6/8] block: dump_qlist() may dereference a Null pointer Liam Merwick
2018-11-05 0:07 ` Max Reitz
2018-11-05 21:38 ` Liam Merwick [this message]
2018-10-19 20:39 ` [Qemu-devel] [PATCH v4 7/8] qcow2: Read outside array bounds in qcow2_pre_write_overlap_check() Liam Merwick
2018-10-19 20:39 ` [Qemu-devel] [PATCH v4 8/8] kvm: Potential NULL pointer dereference in kvm_arch_init_vcpu() Liam Merwick
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=858844d0-9e9d-d25f-b105-d8ddf2a58ab7@oracle.com \
--to=liam.merwick@oracle.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).