From: Gerd Knorr <kraxel@bytesex.org>
To: Henrik Nordstrom <uml@hno.marasystems.com>
Cc: BlaisorBlade <blaisorblade_spam@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net,
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 09:26:09 +0200 [thread overview]
Message-ID: <20041019072608.GD3052@bytesex> (raw)
In-Reply-To: <Pine.LNX.4.61.0410190847370.10629@filer.marasystems.com>
On Tue, Oct 19, 2004 at 08:59:53AM +0200, Henrik Nordstrom wrote:
> If the tracing parent is still alive the natural thing would be to save
> the signal as pending and notify the parent when the child is restarted. A
> SIGKILL to a traced process in my opinion should not kill the traced
> process without allowing the tracing parent to veto on the signal.
Well, if you don't ptrace a process you can't catch/veto the SIGKILL as
well, so why you should be able to do that while ptracing? Beside that
neither the process itself is killed nor the ptracing parent is notified
on SIGKILL.
When the process is _not_ ptraced the SIGKILL works just fine
(unconditionally, no matter whenever the process is stopped or not).
IMHO the behavior should be the same when the process is traced.
Gerd
--
return -ENOSIG;
-------------------------------------------------------
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 7:40 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
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 [this message]
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=20041019072608.GD3052@bytesex \
--to=kraxel@bytesex.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=lorenzo@colitti.com \
--cc=rimondin@dia.uniroma3.it \
--cc=uml@hno.marasystems.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.