[lkml]   [2004]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: get_task_struct()
On Sat, 2004-04-17 at 12:46 -0300, Fabiano Ramos wrote:

> Inside sys_ptrace, the function get_task_struct is invoked after
> retrieving the child's task srtuct pointer. Why is it done? I have
> tracked down the code and noticed that it is in fact an increment
> on the (page?) counter. Can you help me understand it?

Think of get_task_struct(foo) as a reference count on foo's task
structure. So long as the reference count is elevated, foo's task
structure cannot be deallocated.

get_task_struct() is called here because sys_ptrace() needs to ensure
that the child's task structure does not go away out from under this
function, but we do not want to hold the tasklist_lock.

> Is it necessary to call free_task_struct whenever its get counterpart
> is called?

Yes, although it is called "put_task_struct()". It is called at the end
of this function.

Robert Love

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:02    [W:0.049 / U:7.764 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site