From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: paulus@samba.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix off-by-one error in sizing pSeries hcall table
Date: Tue, 10 May 2011 08:10:48 +0200 [thread overview]
Message-ID: <8D1B78A9-031B-4FBA-AAD9-E1700FB9F02F@suse.de> (raw)
In-Reply-To: <1305007581-27570-1-git-send-email-david@gibson.dropbear.id.au>
On 10.05.2011, at 08:06, David Gibson wrote:
> The pSeries machine uses two tables to look up guest hcalls for emulation.
> One of these is exactly one entry too small to hold all the hcalls it needs
> to, leading to memory corruption.
>
> This patch fixes the bug, and while we're at it, make both tables 'static'
> since they're never used from other modules.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Thanks, applied to the ppc-next queue.
Alex
prev parent reply other threads:[~2011-05-10 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 6:06 [Qemu-devel] [PATCH] Fix off-by-one error in sizing pSeries hcall table David Gibson
2011-05-10 6:10 ` Alexander Graf [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=8D1B78A9-031B-4FBA-AAD9-E1700FB9F02F@suse.de \
--to=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@samba.org \
--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).