From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Dan Smith <danms@us.ibm.com>
Subject: Re: [Xen-changelog] Correct buffer->size at the same time as buffer->capacity when shrinking down a
Date: Thu, 17 Nov 2005 11:38:05 -0600 [thread overview]
Message-ID: <437CBFFD.7020007@us.ibm.com> (raw)
In-Reply-To: <E1EcmDE-000875-Pm@xenbits.xensource.com>
Thanks Ewan, Dan and I were banging our heads on this one.
Good Catch!
Regards,
Anthony Liguori
Xen patchbot -unstable wrote:
># HG changeset patch
># User emellor@leeni.uk.xensource.com
># Node ID 418954da5c0f58bc856893f3850b0d97deb143ec
># Parent 3f39f030fa894d29d04b748513bf48000d6a17f5
>Correct buffer->size at the same time as buffer->capacity when shrinking down a
>buffer that has grown beyond max_capacity. This fixes a Xenconsoled segfault
>that was caused by stomping around above the buffer's allocated region. It
>became possible to set the max_capacity with changeset 7431, and ever
>since then we have been exposed to this bug. It would most easily be triggered
>by running a domain without a client attached to the console, so that the
>max_capacity was reached more easily.
>
>Closes bug #380.
>
>Signed-off-by: Ewan Mellor <ewan@xensource.com>
>
>diff -r 3f39f030fa89 -r 418954da5c0f tools/console/daemon/io.c
>--- a/tools/console/daemon/io.c Wed Nov 16 19:33:23 2005
>+++ b/tools/console/daemon/io.c Thu Nov 17 11:59:12 2005
>@@ -114,7 +114,7 @@
> buffer->data, buffer->max_capacity);
> buffer->data = realloc(buffer->data,
> buffer->max_capacity);
>- buffer->capacity = buffer->max_capacity;
>+ buffer->size = buffer->capacity = buffer->max_capacity;
> }
> }
>
>
>_______________________________________________
>Xen-changelog mailing list
>Xen-changelog@lists.xensource.com
>http://lists.xensource.com/xen-changelog
>
>
>
parent reply other threads:[~2005-11-17 17:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1EcmDE-000875-Pm@xenbits.xensource.com>]
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=437CBFFD.7020007@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=danms@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.