All of lore.kernel.org
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: Jeff Dike <jdike@addtoit.com>, Andi Kleen <ak@suse.de>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] x86_64 32-bit ptrace mangles sixth systemcall argument
Date: Mon, 12 Mar 2007 23:12:57 +0100	[thread overview]
Message-ID: <200703122312.57504.blaisorblade@yahoo.it> (raw)
In-Reply-To: <45F52EA7.2090605@fujitsu-siemens.com>

On Monday 12 March 2007 11:42, Bodo Stroesser wrote:
> Blaisorblade wrote:
> > On Tuesday 06 March 2007 00:26, Blaisorblade wrote:
> >  > 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.
> >
> > Hmm, return through IRET is implemented for sys_rt_sigreturn since 2.6.0
> > (with
> > a couple of changes, yeah, but...).
> >
> > Was the original Bodo's report bogus? No, he actually found a much harder
> > issue.
> >
> > I've attached the log of that IRC here for reference.
>
> I took a quick look into 2.6.21-rc3, arch/x86_64/entry.S. AFAICS, the
> problem I supposed in the IRC is fixed. Now a ptraced syscall always
> returns through IRET. Thus, *all* registers in user space exactly will have
> the contents, which the tracing process wrote at end of syscall.

About 32bit emulation (arch/x86_64/ia32/ia32entry.S), it too returns through 
IRET when ptrace is active. Ok.

Now it would then be time to look again at SKAS support? Well, nothing easy it 
seems - I've done a quick test of 32bit UML over 64bit host again and had no 
luck.
-- 
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

      reply	other threads:[~2007-03-12 22:13 UTC|newest]

Thread overview: 10+ 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-01-31 22:45 ` Jeff Dike
2007-02-02 17:48 ` [uml-devel] " 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
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 [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=200703122312.57504.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=ak@suse.de \
    --cc=bstroesser@fujitsu-siemens.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.