From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Werner Almesberger <wa@almesberger.net>,
Chris Wedgwood <cw@f00f.org>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: Why UML often does not build (was: Re: [PATCH] UML: Build fix for TT w/o SKAS)
Date: Fri, 29 Oct 2004 16:53:02 +0200 [thread overview]
Message-ID: <200410291653.02985.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20041029034444.A24523@almesberger.net>
On Friday 29 October 2004 08:44, Werner Almesberger wrote:
> Chris Wedgwood wrote:
> > the problem here is that ptrace semantics are not well defined to
> > anything subtle can and will break from time to time
>
> I wonder what the "correct" solution for this would be: write a
> specification for Linux ptrace, or try to get the POSIX folks
> interested ?
> Given that we get subtle ptrace breakages quite regularly, it
> would be nice to see this eventually get resolved. "The
> implementation is the specification" doesn't seem to work well
> in this case.
Well, you are quite right - Linux is aimed at never breaking existing
binaries, and ptrace() does not follow that.
However, the problem here is that UML was not behaving correctly. Instead of
using the documented way, PTRACE_KILL, we just sent a SIGKILL and that
happened to work (and since PTRACE_KILL implementation just sends a SIGKILL,
you would still expect it to work).
In fact, I fixed the Gerd Knorr test program to use PTRACE_KILL and it works
on 2.6.9.
> BTW, things have improved around UML quite a bit recently, and I
> think this is to no small amount due to Paolo's work.
Thanks a lot for that, it's something very important for me, but I'm not the
only one deserving such recognition. See the amount of work done by Bodo
Stroesser in a few weeks - he solved lots of problems which I fought against
without success.
Besides that, I need to do a lot of janitorial work, while holding on more
advanced stuff - so I think that anybody could be able to help here.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-10-29 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041027053602.GB30735@taniwha.stupidest.org>
[not found] ` <200410282104.30482.blaisorblade_spam@yahoo.it>
[not found] ` <20041028193329.GF851@taniwha.stupidest.org>
2004-10-28 20:54 ` [uml-devel] Why UML often does not build (was: Re: [PATCH] UML: Build fix for TT w/o SKAS) Blaisorblade
2004-10-28 21:42 ` [uml-devel] " Chris Wedgwood
2004-10-28 23:49 ` Blaisorblade
2004-10-29 0:28 ` Chris Wedgwood
2004-10-29 6:44 ` Werner Almesberger
2004-10-29 14:53 ` 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=200410291653.02985.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=wa@almesberger.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