From: "Sven Köhler" <skoehler@upb.de>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>, Roland Kaeser <roli8200@yahoo.de>,
Nuno Silva <nuno.silva@vgertech.com>,
Antoine Martin <antoine@nagafix.co.uk>,
Dennis Muhlestein <devel@muhlesteins.com>
Subject: [uml-devel] Re: Stop at startup on 2.6 NPTL hosts
Date: Wed, 03 Nov 2004 00:43:36 +0100 [thread overview]
Message-ID: <41881BA8.80102@upb.de> (raw)
In-Reply-To: <200411021952.09095.blaisorblade_spam@yahoo.it>
> It is one UML bug I've just identified and that I'm trying to fix. This is the
> faulty code, from arch/um/kernel/skas/process.c:
>
> static int userspace_tramp(void *arg)
> {
> init_new_thread_signals(0);
> enable_timer();
> ptrace(PTRACE_TRACEME, 0, 0, 0);
> tkill(gettid(), SIGSTOP);
> os_stop_process(os_getpid());
> return(0);
> }
>
> This is executed by a clone() child. What happens is that, with NPTL, both the
> father and the son have the same pid, so the SIGSTOP is routed to the wrong
> thread. However, this is not expected: having the same pid should be reserved
> to when clone is called with CLONE_THREAD in the flags. I've verified that
> this is not happening in this case, even with strace (to make sure glibc is
> not playing any dirty tricks). But for some reasons, the kernel is behaving
> as if this happened.
This does remind me of something. I've already read the whole thing with
CLONE_THREAD and clone() somewhere else, but i can't remember where it
was. Was it on UML-MailingLists? Or was it even on the LKML? If my brain
would just be a bit more reliable :-(
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-11-02 23:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 9:26 [uml-devel] UML Kernel 2.6.7 Nothing happens Roland Kaeser
2004-11-02 18:52 ` Stop at startup on 2.6 NPTL hosts (was: Re: [uml-devel] UML Kernel 2.6.7 Nothing happens) Blaisorblade
2004-11-02 23:43 ` Sven Köhler [this message]
2004-11-03 3:04 ` [uml-devel] Re: Stop at startup on 2.6 NPTL hosts Nuno Silva
2004-11-03 8:32 ` Gerd Knorr
2004-11-03 15:59 ` Blaisorblade
2004-11-03 20:10 ` Gerd Knorr
2004-11-03 22:17 ` Blaisorblade
2004-11-04 8:40 ` Nuno Silva
2004-11-09 16:42 ` Bodo Stroesser
2004-11-09 17:29 ` Adam Heath
2004-11-09 17:32 ` Bodo Stroesser
2004-11-09 18:23 ` Bodo Stroesser
2004-11-09 19:11 ` Blaisorblade
2004-11-10 8:36 ` stian
2004-11-10 9:07 ` Geert Uytterhoeven
2004-11-10 12:15 ` Bodo Stroesser
2004-11-10 12:47 ` Geert Uytterhoeven
2004-11-10 14:32 ` Blaisorblade
2004-11-10 14:44 ` Sven Köhler
2004-11-10 21:19 ` Henrik Nordstrom
2004-11-15 17:17 ` Blaisorblade
2004-11-10 17:16 ` 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=41881BA8.80102@upb.de \
--to=skoehler@upb.de \
--cc=antoine@nagafix.co.uk \
--cc=blaisorblade_spam@yahoo.it \
--cc=devel@muhlesteins.com \
--cc=jdike@addtoit.com \
--cc=nuno.silva@vgertech.com \
--cc=roli8200@yahoo.de \
--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