From: Liam Merwick <liam.merwick@oracle.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 4/8] qemu-img: potential Null pointer deref in img_commit()
Date: Fri, 19 Oct 2018 21:32:05 +0100 [thread overview]
Message-ID: <27a60d5c-481a-c8c1-88e7-853ff441b144@oracle.com> (raw)
In-Reply-To: <1d34f37c-94cb-61af-58a6-dae10ddc2ce5@redhat.com>
On 12/10/18 15:51, Max Reitz wrote:
> On 31.08.18 20:16, Liam Merwick wrote:
>> The function block_job_get() may return NULL so before dereferencing
>> the 'job' pointer in img_commit() it should be checked.
>
> It may not because the job yields before executing anything (if it
> started successfully; but otherwise, commit_active_start() would have
> returned an error). Therefore, I think the better solution is to
> assert(job) here.
>
Switched patch to use assert()
Regards,
Liam
> (It would be a serious bug if block_job_get() returned NULL here, so
> it's definitely not something we can be quiet about. But this patch
> makes it so the user doesn't even notice.)
>
> Max
>
>> Signed-off-by: Liam Merwick <Liam.Merwick@oracle.com>
>> Reviewed-by: Darren Kenny <Darren.Kenny@oracle.com>
>> Reviewed-by: Mark Kanda <Mark.Kanda@oracle.com>
>> ---
>> qemu-img.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/qemu-img.c b/qemu-img.c
>> index b12f4cd19b0a..51fe09bd08ed 100644
>> --- a/qemu-img.c
>> +++ b/qemu-img.c
>> @@ -1029,6 +1029,9 @@ static int img_commit(int argc, char **argv)
>> }
>>
>> job = block_job_get("commit");
>> + if (job == NULL) {
>> + goto unref_backing;
>> + }
>> run_block_job(job, &local_err);
>> if (local_err) {
>> goto unref_backing;
>>
>
>
next prev parent reply other threads:[~2018-10-19 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 18:16 [Qemu-devel] [PATCH v3 0/8] off-by-one and NULL pointer accesses detected by static analysis Liam Merwick
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 1/8] configure: Provide option to explicitly disable AVX2 Liam Merwick
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 2/8] job: Fix off-by-one assert checks for JobSTT and JobVerbTable Liam Merwick
2018-10-09 19:09 ` John Snow
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 3/8] block: Null pointer dereference in blk_root_get_parent_desc() Liam Merwick
2018-10-12 14:48 ` Max Reitz
2018-10-19 20:31 ` Liam Merwick
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 4/8] qemu-img: potential Null pointer deref in img_commit() Liam Merwick
2018-10-09 19:23 ` John Snow
2018-10-12 14:51 ` Max Reitz
2018-10-19 20:32 ` Liam Merwick [this message]
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 5/8] block: Fix potential Null pointer dereferences in vvfat.c Liam Merwick
2018-10-12 15:14 ` Max Reitz
2018-10-19 20:31 ` Liam Merwick
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 6/8] block: dump_qlist() may dereference a Null pointer Liam Merwick
2018-10-12 15:22 ` Max Reitz
2018-10-19 20:34 ` Liam Merwick
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 7/8] io: potential unnecessary check in qio_channel_command_new_spawn() Liam Merwick
2018-08-31 18:16 ` [Qemu-devel] [PATCH v3 8/8] qcow2: Read outside array bounds in qcow2_pre_write_overlap_check() Liam Merwick
2018-10-12 15:24 ` Max Reitz
2018-10-09 16:45 ` [Qemu-devel] [PATCH v3 0/8] off-by-one and NULL pointer accesses detected by static analysis Markus Armbruster
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=27a60d5c-481a-c8c1-88e7-853ff441b144@oracle.com \
--to=liam.merwick@oracle.com \
--cc=mreitz@redhat.com \
--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).