From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-user@lists.sourceforge.net
Cc: Gerd Knorr <kraxel@bytesex.org>,
user-mode-linux-devel@lists.sourceforge.net,
Lorenzo Colitti <lorenzo@colitti.com>,
Massimo Rimondini <rimondin@dia.uniroma3.it>
Subject: [uml-devel] Re: [uml-user] Host processes never terminate on 2.6.9rc3 host (stuck in ptrace_stop)
Date: Tue, 19 Oct 2004 00:23:14 +0200 [thread overview]
Message-ID: <200410190023.14067.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20041018212612.GA3052@bytesex>
On Monday 18 October 2004 23:26, Gerd Knorr wrote:
> > > Yes, I see that as well, it actually *is* that ptrace change added in
> > > patch-2.6.9-rc1-bk16.
> > >
> > > IMHO it is a bug, I've reported it to lkml a
> > > few days ago, no response yet.
> >
> > Oh well, did I lost it or you did not CC the UML mailing list? And in the
> > 2nd case, why?
> I didn't cc the uml list as it isn't a uml bug, its just that uml
> triggeres it.
Hmm - trying to fix that or just reverting the patch inside the SKAS patch (or
as attached patch) would have been a possible workaround.
> > I'm downloading the patches from BitKeeper.
>
> I'll attach the offending one for reference, also a short test app
> showing the buggy behavior.
> > > Problem is that you can't kill -9 processes any more which are ptraced
> > > _and_ stopped at the same time.
> >
> > Sorry, tried kill -CONT? I'm almost sure it works (tried by both Henrik
> > Normstrod and me, not in this case).
> IMHO it is a clear bug in the (host) kernel, so I didn't attempt yet to
> workaround that by playing tricks in the UML kernel. I can't see the
> bug when reading the patch through, probably the separation of stopped
> and traced process states triggeres some odd corner case somewhere else
> in the kernel ...
>
> If you send a SIGKILL to the process being stopped & ptraced *nothing*
> happens. Neither the process is killed nor the ptracing parent is
> notified. That can't be correct.
Can you try using SIGCONT, please? Even the patch changelog clearly says that
you must kill -CONT before kill -KILL (actually, a kill -CONT may make the
process notice the SIGKILL), and that behaviour can be reproduced, I think,
on every kernel version. There has been a thread on this (t-mode processes)
on uml-devel. Quite frankly, I do not know the question myself - but people
seem to agree that this is a correct behaviour.
That said, I'll give a look to the patch. Have you CC'ed the patch author on
your report?
--
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-18 22:22 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 [this message]
2004-10-19 5:00 ` Werner Almesberger
2004-10-19 15:47 ` BlaisorBlade
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=200410190023.14067.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 \
/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