Skip to contentSkip to conversation

ptrace: introduce the empty "struct ptrace_task"

RFC PATCH In review Oleg Nesterov 3 participants 5 messages May 25, 2009 – May 26, 2009

Subsystems (5)
lore
Share & tools
lore

Oleg Nesterov

author maintainer
#0 lore raw

RFC PATCH 1/1 ptrace: introduce the empty "struct ptrace_task"

Suggested by Roland.

Introduce the new "struct ptrace_task" and add the pointer to task_struct. The next patches will move all ptrace-related fields from task_struct into this struct. From now, if the task was ever ptraced it has ->ptrace_task != NULL. Freed by free_task() along with task_struct itself.

With utrace based ptrace we can move this struct into utrace_engine->data.

 include/linux/sched.h     |    1 +
 include/linux/ptrace.h    |    4 ++++
 include/linux/tracehook.h |   30 ++++++++++++++++++++++++++++++
 kernel/fork.c             |    5 +++++
 kernel/ptrace.c           |   27 ++++++++++++++++++++++++++-
 5 files changed, 66 insertions(+), 1 deletion(-)
include/linux/sched.h renamed from include/linux/sched.h~3_STRUCT +1 -0
@@ -1201,6 +1201,7 @@ struct task_struct {
 	struct list_head sibling;	/* linkage in my parent's children list */
 	struct task_struct *group_leader;	/* threadgroup leader */
 
+	struct ptrace_task *ptrace_task;
 	/*
 	 * ptraced is the list of tasks this task is using ptrace on.
 	 * This includes both natural children and PTRACE_ATTACH targets.
include/linux/ptrace.h renamed from include/linux/ptrace.h~3_STRUCT +4 -0
@@ -79,6 +79,10 @@
 #include <linux/compiler.h>		/* For unlikely.  */
 #include <linux/sched.h>		/* For struct task_struct.  */
 
+struct ptrace_task {
+};
+
+extern int alloc_ptrace_task(struct task_struct *child);
 
 extern long arch_ptrace(struct task_struct *child, long request, long addr, long data);
 extern int ptrace_traceme(void);
include/linux/tracehook.h renamed from include/linux/tracehook.h~3_STRUCT +30 -0
@@ -243,6 +243,36 @@ static inline int tracehook_prepare_clon
 }
 
 /**
+ * tracehook_init_task - initialize the new child
+ * @child:		new child task
+ * @clone_flags:	%CLONE_* flags from clone/fork/vfork system call
+ * @trace:		return value from tracehook_prepare_clone()
+ *
+ * This is called immediately after dup_task_struct().
+ *
+ * Called with no locks held.
+ */
+static inline int tracehook_init_task(struct task_struct *child,
+					unsigned long clone_flags, int trace)
+{
+	child->ptrace_task = NULL;
+	if (unlikely((clone_flags & CLONE_PTRACE) || trace))
+		return alloc_ptrace_task(child);
+	return 0;
+}
+
+/**
+ * tracehook_free_task - task is about to be freed
+ * @task:		task that will be freed
+ *
+ * May be called from any context.
+ */
+static inline void tracehook_free_task(struct task_struct *task)
+{
+	kfree(task->ptrace_task);
+}
+
+/**
  * tracehook_finish_clone - new child created and being attached
  * @child:		new child task
  * @clone_flags:	%CLONE_* flags from clone/fork/vfork system call
kernel/fork.c renamed from kernel/fork.c~3_STRUCT +5 -0
@@ -143,6 +143,7 @@ void free_task(struct task_struct *tsk)
 	free_thread_info(tsk->stack);
 	rt_mutex_debug_task_free(tsk);
 	ftrace_graph_exit_task(tsk);
+	tracehook_free_task(tsk);
 	free_task_struct(tsk);
 }
 EXPORT_SYMBOL(free_task);
@@ -982,6 +983,10 @@ static struct task_struct *copy_process(
 	if (!p)
 		goto fork_out;
 
+	retval = tracehook_init_task(p, clone_flags, trace);
+	if (retval)
+		goto bad_fork_free;
+
 	rt_mutex_init_task(p);
 
 #ifdef CONFIG_PROVE_LOCKING
kernel/ptrace.c renamed from kernel/ptrace.c~3_STRUCT +26 -1
@@ -174,6 +174,23 @@ bool ptrace_may_access(struct task_struc
 	return !err;
 }
 
+int alloc_ptrace_task(struct task_struct *tsk)
+{
+	struct ptrace_task *ptrace_task;
+
+	if (tsk->ptrace_task)
+		return 0;
+
+	ptrace_task = kzalloc(sizeof(*ptrace_task), GFP_KERNEL);
+	if (unlikely(!ptrace_task))
+		return -ENOMEM;
+
+	if (cmpxchg(&tsk->ptrace_task, NULL, ptrace_task) != NULL)
+		kfree(ptrace_task);
+
+	return 0;
+}
+
 int ptrace_attach(struct task_struct *task)
 {
 	int retval;
@@ -199,6 +216,10 @@ int ptrace_attach(struct task_struct *ta
 	if (retval)
 		goto unlock_creds;
 
+	retval = alloc_ptrace_task(task);
+	if (unlikely(retval))
+		goto unlock_creds;
+
 	write_lock_irq(&tasklist_lock);
 	retval = -EPERM;
 	if (unlikely(task->exit_state))
@@ -230,8 +251,12 @@ out:
  */
 int ptrace_traceme(void)
 {
-	int ret = -EPERM;
+	int ret = alloc_ptrace_task(current);
+
+	if (unlikely(ret))
+		return ret;
 
+	ret = -EPERM;
 	write_lock_irq(&tasklist_lock);
 	/* Are we already being traced? */
 	if (!task_ptrace(current)) {
#1 lore raw

include/linux/sched.h struct task_struct { · line 1207

Quoted 10 lines · Oleg Nesterov
include/linux/sched.h renamed from include/linux/sched.h~3_STRUCT +1 -0
@@ -1201,6 +1201,7 @@ struct task_struct {
 	struct list_head sibling;	/* linkage in my parent's children list */
 	struct task_struct *group_leader;	/* threadgroup leader */
 
+	struct ptrace_task *ptrace_task;
 	/*
 	 * ptraced is the list of tasks this task is using ptrace on.
 	 * This includes both natural children and PTRACE_ATTACH targets.

the naming sucks.

Please use 'struct ptrace_context' and '*ptrace_ctx' instead.

Thanks,

Ingo

author maintainer
#2 lore raw
Quoted 9 lines · Ingo Molnar
Quoted 6 lines · Oleg Nesterov
include/linux/sched.h renamed from include/linux/sched.h~3_STRUCT +0 -0
@@ -1201,6 +1201,7 @@ struct task_struct {
 	struct list_head sibling;	/* linkage in my parent's children list */
 	struct task_struct *group_leader;	/* threadgroup leader */
 
Quoted 8 lines

include/linux/sched.h struct task_struct { · line 1207

Quoted 4 lines
include/linux/sched.h renamed from include/linux/sched.h~3_STRUCT +1 -0
+	struct ptrace_task *ptrace_task;
 	/*
 	 * ptraced is the list of tasks this task is using ptrace on.
 	 * This includes both natural children and PTRACE_ATTACH targets.

the naming sucks.

Please use 'struct ptrace_context' and '*ptrace_ctx' instead.

As always, I agree with any naming. Will re-name in V2.

Oleg.

#3 lore raw
In reply to Ingo Molnar
Quoted 1 line

Please use 'struct ptrace_context' and '*ptrace_ctx' instead.

I am fine with this name (or any other). But note in considering your suggestions that we will shortly have another separate struct with a similar name. The first one is the state of a ptrace tracee task (bits about itself and pointing to its tracer). The second is the state of a ptrace tracer (head of its tracees list, locks, etc).

A name like "ptrace_context" could be read as intuitive for either of these two quite different things. Perhaps this is true of "ptrace_task" too, though it seemed to us like it wasn't too unclear, and preferably shorter than something like "ptrace_tracee_context".

Thanks,
Roland

#4 lore raw
In reply to Oleg Nesterov
Quoted 3 lines

/**
+ * tracehook_init_task - initialize the new child
+ * @child: new child task

s/child/task/

Quoted 4 lines

+ * @clone_flags: %CLONE_* flags from clone/fork/vfork system call
+ * @trace: return value from tracehook_prepare_clone()
+ *
+ * This is called immediately after dup_task_struct().

* It must clear/reset any tracing state so that tracehook_free_task()
* will work safely if the task creation fails. If the task creation
* succeeds, a tracehook_finish_clone() call will follow with locks
* held, before @task starts or is accessible to anyone else.

Quoted 1 line

+int alloc_ptrace_task(struct task_struct *tsk)

This deserves a short comment about the context it's called from, and when it is or isn't called at all.

kernel/ptrace.c bool ptrace_may_access(struct task_struc · line 189

Quoted 2 lines
kernel/ptrace.c renamed from kernel/ptrace.c~3_STRUCT +2 -0
+	if (cmpxchg(&tsk->ptrace_task, NULL, ptrace_task) != NULL)
+		kfree(ptrace_task);

I don't see cmpxchg() used very often at all in generic kernel code. I wonder how good a choice it is across every arch. Is there a reason not to use e.g. task_lock() to mediate installing a new ->ptrace_task pointer? That seems like a more conservative route.

Thanks,
Roland