From: Fabiano Rosas <farosas@suse.de>
To: Dmitry Frolov <frolov@swemel.ru>,
Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
qemu-devel@nongnu.org
Cc: sdl.qemu@linuxtesting.org, Dmitry Frolov <frolov@swemel.ru>
Subject: Re: [PATCH v1] migration: fix RAMBlock add NULL check
Date: Tue, 10 Oct 2023 10:36:04 -0300 [thread overview]
Message-ID: <87o7h6sipn.fsf@suse.de> (raw)
In-Reply-To: <20231010104851.802947-1-frolov@swemel.ru>
Dmitry Frolov <frolov@swemel.ru> writes:
> qemu_ram_block_from_host() may return NULL, which will be dereferenced w/o
> check. Usualy return value is checked for this function.
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: c7c0e72408df5e7821c0e995122fb2fe0ac001f1 ("migration/ram: Handle RAM block resizes during precopy")
> Signed-off-by: Dmitry Frolov <frolov@swemel.ru>
> ---
> migration/ram.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index e4bfd39f08..bd4b7574e1 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -4281,6 +4281,11 @@ static void ram_mig_ram_block_resized(RAMBlockNotifier *n, void *host,
> RAMBlock *rb = qemu_ram_block_from_host(host, false, &offset);
> Error *err = NULL;
>
> + if (!rb) {
> + error_report("RAM block not found");
> + return;
> + }
> +
> if (migrate_ram_is_ignored(rb)) {
> return;
> }
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2023-10-10 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 10:48 [PATCH v1] migration: fix RAMBlock add NULL check Dmitry Frolov
2023-10-10 13:36 ` Fabiano Rosas [this message]
2023-10-10 19:23 ` Peter Xu
2023-10-11 13:20 ` Дмитрий Фролов
2023-10-11 14:24 ` Peter Xu
2023-10-11 14:33 ` Juan Quintela
2023-10-11 14:36 ` Дмитрий Фролов
2023-10-11 13:07 ` Juan Quintela
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=87o7h6sipn.fsf@suse.de \
--to=farosas@suse.de \
--cc=frolov@swemel.ru \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=sdl.qemu@linuxtesting.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).