From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6412] linux-user: add qemu_realloc() implementation to unbreak the build ( Gerd Hoffman)
Date: Fri, 23 Jan 2009 16:38:34 +0100 [thread overview]
Message-ID: <761ea48b0901230738j451cd69bqcf4d394950a99b52@mail.gmail.com> (raw)
In-Reply-To: <E1LQNY5-00076m-Fd@cvs.savannah.gnu.org>
On Fri, Jan 23, 2009 at 4:02 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Revision: 6412
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6412
> Author: aliguori
> Date: 2009-01-23 15:02:20 +0000 (Fri, 23 Jan 2009)
>
> Log Message:
> -----------
> linux-user: add qemu_realloc() implementation to unbreak the build (Gerd Hoffman)
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>
> Modified Paths:
> --------------
> trunk/linux-user/mmap.c
>
> Modified: trunk/linux-user/mmap.c
> ===================================================================
> --- trunk/linux-user/mmap.c 2009-01-22 22:09:55 UTC (rev 6411)
> +++ trunk/linux-user/mmap.c 2009-01-23 15:02:20 UTC (rev 6412)
> @@ -123,6 +123,19 @@
> munmap(p, *p);
> }
>
> +void *qemu_realloc(void *ptr, size_t size)
> +{
> + size_t old_size, copy;
> + void *new_ptr;
> +
> + old_size = *(size_t *)((char *)ptr - 16);
> + copy = old_size < size ? old_size : size;
> + new_ptr = qemu_malloc(size);
> + memcpy(new_ptr, ptr, copy);
> + qemu_free(ptr);
> + return new_ptr;
> +}
Is it really the correct fix? The original error comes from the fact
we compile qemu_iovec_* in cutils.c. Do we really need these
iovec functions for user-mode?
Laurent
next prev parent reply other threads:[~2009-01-23 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 15:02 [Qemu-devel] [6412] linux-user: add qemu_realloc() implementation to unbreak the build ( Gerd Hoffman) Anthony Liguori
2009-01-23 15:38 ` Laurent Desnogues [this message]
2009-01-23 16:35 ` Anthony Liguori
2009-01-23 17:15 ` Laurent Desnogues
2009-01-23 18:52 ` Paul Brook
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=761ea48b0901230738j451cd69bqcf4d394950a99b52@mail.gmail.com \
--to=laurent.desnogues@gmail.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).