From: David Mosberger <davidm@napali.hpl.hp.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, roland@redhat.com
Subject: comment "ptrace_list" and "children" members
Date: Wed, 28 Jul 2004 10:26:33 -0700 [thread overview]
Message-ID: <16647.57801.568015.688380@napali.hpl.hp.com> (raw)
A while ago I had a "fun" time sorting out how the "ptrace_children"
and the "children" lists are being used. I think the two little
comments would help making that process a lot easier (they're based on
an earlier email by Roland).
--david
Document the purpose of the "ptrace_list/ptrace_children" and
"children/sibling" lists.
Signed-off-by: davidm@hpl.hp.com
===== include/linux/sched.h 1.179 vs edited =====
--- 1.179/include/linux/sched.h 2004-07-06 22:19:25 -07:00
+++ edited/include/linux/sched.h 2004-07-20 21:57:10 -07:00
@@ -410,6 +410,10 @@
unsigned int time_slice, first_time_slice;
struct list_head tasks;
+ /*
+ * ptrace_list/ptrace_children forms the list of my children
+ * that were stolen by a ptracer.
+ */
struct list_head ptrace_children;
struct list_head ptrace_list;
@@ -431,6 +435,10 @@
*/
struct task_struct *real_parent; /* real parent process (when being debugged) */
struct task_struct *parent; /* parent process */
+ /*
+ * children/sibling forms the list of my children plus the
+ * tasks I'm ptracing.
+ */
struct list_head children; /* list of my children */
struct list_head sibling; /* linkage in my parent's children list */
struct task_struct *group_leader; /* threadgroup leader */
next reply other threads:[~2004-07-28 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 17:26 David Mosberger [this message]
2004-07-28 17:30 ` Roland McGrath
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=16647.57801.568015.688380@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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
all inboxes | Powered by JetHome®