From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
xen-devel <xen-devel@lists.xensource.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Michael Abd-El-Malek <mabdelmalek@cmu.edu>
Subject: Re: [Xen-devel] [PATCH] xen: Fix grant table bug
Date: Thu, 03 Apr 2008 07:36:39 -0700 [thread overview]
Message-ID: <47F4EB77.1010304@goop.org> (raw)
In-Reply-To: <1207229210.29720.11.camel@muff>
Mark McLoughlin wrote:
> On Sun, 2008-03-30 at 23:42 -0400, Michael Abd-El-Malek wrote:
>
>
>> There was a bug in the free list allocation code. The free list was indexed as
>> if it was the same size as the grant table. But it's only half as large. So
>> memory got corrupted, and I was seeing crashes in the slab allocator later on.
>>
>
> Looks like an obvious candidate for upstream linux too. Rebased version
> below.
>
Queued, thanks.
J
prev parent reply other threads:[~2008-04-03 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47F05DB1.5090606@cmu.edu>
2008-04-03 13:26 ` [PATCH] xen: Fix grant table bug Mark McLoughlin
2008-04-03 14:36 ` Jeremy Fitzhardinge [this message]
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=47F4EB77.1010304@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mabdelmalek@cmu.edu \
--cc=markmc@redhat.com \
--cc=mingo@elte.hu \
--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 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).