From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [PATCH] x86_64 32-bit ptrace mangles sixth system call argument
Date: Tue, 6 Mar 2007 00:26:53 +0100 [thread overview]
Message-ID: <200703060026.53253.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20070305231044.GB9525@ccure.user-mode-linux.org>
On Tuesday 06 March 2007 00:10, Jeff Dike wrote:
> On Tue, Mar 06, 2007 at 12:03:26AM +0100, Blaisorblade wrote:
> > > No, RCX corruption is different - that happens when a sysexit is done
> > > from a system call where userspace wasn't prepared to save and restore
> > > RCX. sigreturn is the best example.
> > Hmm... we should finally fix that, at some point. Or... now that you
> > explain it this way, it could even seem unfixable... is it? Or maybe
> > sysreturn should become a syscall where the return must happen through
> > the slow return path (iret), if that exists for x86_64.
> This is fixed, and has been for a while. The fix was, as you suggest,
> return through iret in this case.
Also the 32bit emulation case? That would be interesting for SKAS with 64bit
host and 32bit guest (which I haven't tested for a long time). Also this
means that I could test the needed trivial fixes for 64 on 64 (like
opening /proc/mm64, using PTRACE_EX_FAULTINFO which I introduced...).
--
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-03-05 23:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 22:45 [uml-devel] [PATCH] x86_64 32-bit ptrace mangles sixth system call argument Jeff Dike
2007-02-02 17:48 ` Blaisorblade
2007-02-02 20:12 ` Jeff Dike
2007-03-05 23:03 ` Blaisorblade
2007-03-05 23:10 ` Jeff Dike
2007-03-05 23:26 ` Blaisorblade [this message]
2007-03-09 21:50 ` Blaisorblade
2007-03-12 10:42 ` [uml-devel] [PATCH] x86_64 32-bit ptrace mangles sixth systemcall argument Bodo Stroesser
2007-03-12 22:12 ` Blaisorblade
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=200703060026.53253.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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