qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [REGRESSION] mprotect in guest makes qemu-i386 crash
Date: Mon, 07 Jul 2008 14:40:40 +0200	[thread overview]
Message-ID: <48720EC8.3000408@siemens.com> (raw)
In-Reply-To: <486CECB1.8000504@siemens.com>

Jan Kiszka wrote:
> Hi,
> 
> this fragment from a code self-modification test of mine used to work a
> few weeks ago with qemu-i386 userspace emulation. Now it causes a segfault.
> 
> #include <sys/mman.h>
> main()
> {
> 	mprotect((void *)((unsigned long)main & ~0xfff), 0x1000,
> 		 PROT_READ|PROT_WRITE|PROT_EXEC);
> }
> 
> qemu-x86_64 even complains about an "Unsupported syscall: 221", while
> the same 64-bit binary works fine with 0.9.1 (I don't recall anymore if
> it worked recently with SVN head).

Some clarification: mprotect is fine with qemu-x86_64, that syscall
warning is another, unrelated issue (it pops up with every x86_64
application in userland emu).

That leaves us with mprotect being broken in qemu-i386 on x86_64 hosts.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

      reply	other threads:[~2008-07-07 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 15:13 [Qemu-devel] [REGRESSION] mprotect in guest makes qemu-i386 crash Jan Kiszka
2008-07-07 12:40 ` 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=48720EC8.3000408@siemens.com \
    --to=jan.kiszka@siemens.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).