From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xensource.com>
Subject: Re: [Qemu-devel] qemu/pci: Unaligned config read/write overflow
Date: Wed, 29 Nov 2006 14:51:24 +0000 [thread overview]
Message-ID: <fb249edb0611290651h5f179a44w5e66779e751aa83d@mail.gmail.com> (raw)
In-Reply-To: <20061128040441.GA7506@gondor.apana.org.au>
Hi,
On 28/11/06, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> The default config read/write handlers allows a 4-byte read/write at
> address 255. This can clobber the field after the config area. This
> happens to be the PCIBus pointer in the PCIDevice structure.
An easier way to prevent the clobbering is grow PCIDevice::config by
three bytes.
Regards,
Andrew
prev parent reply other threads:[~2006-11-29 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 4:04 [Qemu-devel] qemu/pci: Unaligned config read/write overflow Herbert Xu
2006-11-29 14:51 ` andrzej zaborowski [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=fb249edb0611290651h5f179a44w5e66779e751aa83d@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@gmail.com \
--cc=keir@xensource.com \
--cc=qemu-devel@nongnu.org \
--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).