From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Werner Almesberger <wa@almesberger.net>,
user-mode-linux-user@lists.sourceforge.net,
Gerd Knorr <kraxel@bytesex.org>,
Lorenzo Colitti <lorenzo@colitti.com>,
Massimo Rimondini <rimondin@dia.uniroma3.it>
Subject: Re: [uml-devel] Re: [uml-user] Host processes never terminate on 2.6.9rc3 host (stuck in ptrace_stop)
Date: Tue, 19 Oct 2004 17:47:49 +0200 [thread overview]
Message-ID: <200410191747.49906.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20041019020055.A31791@almesberger.net>
On Tuesday 19 October 2004 07:00, Werner Almesberger wrote:
> BlaisorBlade wrote:
> > Can you try using SIGCONT, please? Even the patch changelog clearly says
> > that you must kill -CONT before kill -KILL
>
> That looks like a race condition.
> If the process manages to enter
> the same state again before you get to KILL it,
Why? This does not make sense, IMHO - after a SIGCONT it should keep running
until something *requests* it stopping - or not? I'm not finding a clue in
the sources... it's quite difficult.
> even this "advanced"
> kill is lost.
> > (actually, a kill -CONT may make the process notice the SIGKILL),
> That's what works so far, yes. I'm actually no quite certain what
> this thread is about: it sounds as if this was a new problem, but
> we've required CONT with KILL in some cases already for a long
> time.
> > Quite frankly, I do not know the question myself - but people
> > seem to agree that this is a correct behaviour.
> The odd thing is that a process that was ptraced but whose ptracer
> is long dead *still* needs the CONT. That doesn't look right to me.
I remember that on Slackware, when doing "init 1" it sends even kill -CONT to
all processes, so either they think it's correct or they want to workaround
an issue existing for lots of kernel releases.
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
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-10-19 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4173F1FD.6080004@colitti.com>
[not found] ` <87d5zgrkm2.fsf@bytesex.org>
2004-10-18 19:18 ` [uml-devel] Re: [uml-user] Host processes never terminate on 2.6.9rc3 host (stuck in ptrace_stop) BlaisorBlade
2004-10-18 21:26 ` Gerd Knorr
2004-10-18 22:23 ` BlaisorBlade
2004-10-19 5:00 ` Werner Almesberger
2004-10-19 15:47 ` BlaisorBlade [this message]
2004-10-19 16:15 ` Werner Almesberger
2004-10-19 17:58 ` Gerd Knorr
2004-10-20 23:54 ` Michael Richardson
2004-10-21 7:57 ` Gerd Knorr
2004-10-19 6:59 ` Henrik Nordstrom
2004-10-19 7:26 ` Gerd Knorr
2004-10-19 8:47 ` Henrik Nordstrom
2004-10-19 9:04 ` Gerd Knorr
2004-10-19 7:18 ` Gerd Knorr
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=200410191747.49906.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=kraxel@bytesex.org \
--cc=lorenzo@colitti.com \
--cc=rimondin@dia.uniroma3.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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