From: Jan Kiszka <jan.kiszka@web.de>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: Turn gdt_table into local variable
Date: Mon, 14 Jul 2008 09:14:48 +0200 [thread overview]
Message-ID: <487AFCE8.1060006@web.de> (raw)
In-Reply-To: <200807132311.18504.paul@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Paul Brook wrote:
> On Sunday 13 July 2008, Jan Kiszka wrote:
>> qemu_malloc[z] does not return memory suited for direct guest access,
>> but that is mandatory for gdt_table. Local host variables are safe,
>
> No they aren't.
Well, right (even when renaming local to global - what I actually
meant). It is safer, but some risk remains that global variables are
mapped to high addresses.
Due to this and also because of some further bug of that kind I found in
the meantime a better series is on the way.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2008-07-14 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 20:28 [Qemu-devel] [PATCH] linux-user: Turn gdt_table into local variable Jan Kiszka
2008-07-13 22:11 ` Paul Brook
2008-07-14 7:14 ` Jan Kiszka [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=487AFCE8.1060006@web.de \
--to=jan.kiszka@web.de \
--cc=paul@codesourcery.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).