From: Igor Mammedov <imammedo@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Richard Henderson <rth@twiddle.net>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/2] memory-device: turn alignment assert into check
Date: Fri, 8 Jun 2018 10:28:55 +0200 [thread overview]
Message-ID: <20180608102855.0d4005e4@redhat.com> (raw)
In-Reply-To: <20180607154705.6316-2-david@redhat.com>
On Thu, 7 Jun 2018 17:47:04 +0200
David Hildenbrand <david@redhat.com> wrote:
> The start of the address space indicates which maximum alignment is
> supported by our machine (e.g. ppc, x86 1GB). This is helpful to
> catch fragmenting guest physical memory in strange fashions.
>
> Right now we can crash QEMU by e.g. (there might be easier examples)
>
> qemu-system-x86_64 -m 256M,maxmem=20G,slots=2 \
> -object memory-backend-file,id=mem0,size=8192M,mem-path=/dev/zero,align=8192M \
> -device pc-dimm,id=dimm1,memdev=mem0
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> hw/mem/memory-device.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
> index 3e04f3954e..6de4f70bb4 100644
> --- a/hw/mem/memory-device.c
> +++ b/hw/mem/memory-device.c
> @@ -116,9 +116,15 @@ uint64_t memory_device_get_free_addr(MachineState *ms, const uint64_t *hint,
> address_space_start = ms->device_memory->base;
> address_space_end = address_space_start +
> memory_region_size(&ms->device_memory->mr);
> - g_assert(QEMU_ALIGN_UP(address_space_start, align) == address_space_start);
> g_assert(address_space_end >= address_space_start);
>
> + /* address_space_start indicates the maximum alignment we expect */
> + if (QEMU_ALIGN_UP(address_space_start, align) != address_space_start) {
> + error_setg(errp, "the alignment (0%" PRIx64 ") is not supported",
> + align);
> + return 0;
> + }
> +
> memory_device_check_addable(ms, size, errp);
> if (*errp) {
> return 0;
next prev parent reply other threads:[~2018-06-08 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:47 [Qemu-devel] [PATCH v1 0/2] memory: fix alignment checks/asserts David Hildenbrand
2018-06-07 15:47 ` [Qemu-devel] [PATCH v1 1/2] memory-device: turn alignment assert into check David Hildenbrand
2018-06-08 8:28 ` Igor Mammedov [this message]
2018-06-07 15:47 ` [Qemu-devel] [PATCH v1 2/2] exec: check that alignment is a power of two David Hildenbrand
2018-06-08 8:30 ` Igor Mammedov
2018-06-07 22:01 ` [Qemu-devel] [PATCH v1 0/2] memory: fix alignment checks/asserts Michael S. Tsirkin
2018-06-11 13:30 ` Paolo Bonzini
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=20180608102855.0d4005e4@redhat.com \
--to=imammedo@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.