Messages in this thread Patch in this message | | | From | David Mosberger <> | Date | Wed, 28 Jul 2004 10:26:33 -0700 | Subject | comment "ptrace_list" and "children" members |
| |
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 */ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |