From: Jeff Dike <jdike@addtoit.com>
To: "Stroesser, Bodo" <Bodo.Stroesser@fujitsu-siemens.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
BlaisorBlade <blaisorblade_spam@yahoo.it>
Subject: Re: [uml-devel] Minor problems with interrupted systemcalls
Date: Wed, 29 Sep 2004 17:10:40 -0400 [thread overview]
Message-ID: <200409292110.i8TLAeLR003432@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Wed, 29 Sep 2004 18:34:14 +0200." <8B6FF516CBA0194AB0996705076B02520F7C3D@ABGEX01E.abg.fsc.net>
Bodo.Stroesser@fujitsu-siemens.com said:
> A small piece of code regarding SA_ONESHOT should be removed only. In
> 2.6.9 this is done in get_signal_to_deliver(), and since
> get_signal_to_deliver() writes a copy of the corresponding k_sigaction
> into caller's ka_copy, it is a real NOOP.
Yup, I was looking at that when I was pulling your patch apart, but decided
to leave it alone for now. I just got rid of it.
On the subject of escaping from UML, I have a exploit lying around from when
I fixed the bug in tt mode, and it fails to escape in skas mode. I'm not
sure why, though.
I'm also uncertain about sysenter. It should go through the same ptrace path
as int 0x80, and be intercepted in the same way, and a quick look at entry.S
indicates that it does. The remaining question is whether syscall restarting
works the same, and I don't see any x86 code looking at the syscall instruction
before deciding to subtract 2 bytes from eip.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-09-29 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 16:34 [uml-devel] Minor problems with interrupted systemcalls Stroesser, Bodo
2004-09-29 21:10 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-22 17:12 Stroesser, Bodo
2004-09-24 21:32 ` Jeff Dike
2004-09-24 21:32 ` Jeff Dike
2004-09-24 21:32 ` Jeff Dike
2004-09-24 21:32 ` Jeff Dike
2004-09-24 21:32 ` Jeff Dike
2004-09-20 10:06 Stroesser, Bodo
2004-09-21 17:31 ` BlaisorBlade
2004-09-17 17:46 Stroesser, Bodo
2004-09-18 16:17 ` 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=200409292110.i8TLAeLR003432@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=Bodo.Stroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--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