From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Henrik Nordstrom <uml@hno.marasystems.com>
Cc: user-mode-linux-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] T-mode processes
Date: Sun, 03 Oct 2004 14:39:27 -0400 [thread overview]
Message-ID: <30745.1096828767@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Henrik Nordstrom <uml@hno.marasystems.com> of "Sun, 03 Oct 2004 19:55:30 +0200." <Pine.LNX.4.61.0410031940080.16875@filer.marasystems.com>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Henrik" == Henrik Nordstrom <uml@hno.marasystems.com> writes:
>> It may well be, but it isn't acceptable. What would break if
>> kill-9 got rid of processes being PTRACE'ed?
Henrik> This discussion probably is more related to lkml than uml..
Sure.
Henrik> For one thing the SIGKILL needs to be notified to and acted
Henrik> upon by the tracing parent process before it is delivered to
Henrik> the killed process. It is possible (and certainly so in case
Henrik> of UML) that the tracing parent wants to do something
Henrik> entirely different when a traced whild receives SIGKILL or
Henrik> other terminal action.
I can't see a use for this :-)
At least, when the tracing process has gone away, then the SIGKILL
should take effect.
Henrik> The actual question is why a process can be left in traced
Henrik> state without any parent tracing it.. You'll see the same
Henrik> symptoms if you strace a process and then kills strace. My
Henrik> guess is that this is from the basic question on how to
Henrik> determine what to do with the traced process when the
Henrik> tracing parent disappears without telling what the future
Henrik> fate of this process should be.. neither killing or
Henrik> untracing the process is safe options.
Henrik> Any way, sending a SIGCONT to the stopped process gets it
Henrik> going again, or killed in case a SIGKILL or other terminal
Henrik> action is pending.
Our test bed produces a dozen of these every night.
If someone has an idea on how to get better intel on this, I'm happy
to cooperate.
- --
] "Elmo went to the wrong fundraiser" - The Simpson | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQWBHXoqHRg3pndX9AQEa6QP/TueVomIuseyLAuF9ZyUadncSwrQXIM3H
aGBul3l1mmtCr34G0f1vJItvWXUW1MDLZ+hHiFIIh63zkeOWboklKMrRbSPxFC13
Er2peBRxNZ+EGUosEQaMcKktxHn9ktoWifHzcOwvUITTVp4DT+Sp9AuTNObMqTBG
ZIEPnFmjPSg=
=Vub3
-----END PGP SIGNATURE-----
-------------------------------------------------------
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-03 18:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 0:26 [uml-devel] T-mode processes Michael Richardson
2004-10-03 10:41 ` Henrik Nordstrom
2004-10-03 17:26 ` Michael Richardson
2004-10-03 17:55 ` Henrik Nordstrom
2004-10-03 18:39 ` Michael Richardson [this message]
2004-10-04 18:22 ` BlaisorBlade
2004-10-04 22:40 ` Michael Richardson
2004-10-03 15:04 ` BlaisorBlade
2004-10-03 17:44 ` Michael Richardson
2004-10-04 18:57 ` BlaisorBlade
2004-10-04 20:25 ` Henrik Nordstrom
2004-10-05 18:51 ` BlaisorBlade
2004-10-06 0:00 ` Henrik Nordstrom
2004-10-06 19:45 ` BlaisorBlade
2004-10-14 16:46 ` 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=30745.1096828767@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox