tracehook_finish_clone(9) [suse man page]

TRACEHOOK_FINISH_CLO(9) 					 Kernel Internals					   TRACEHOOK_FINISH_CLO(9)

NAME

       tracehook_finish_clone - new child created and being attached

SYNOPSIS

       void tracehook_finish_clone(struct task_struct * child, unsigned long clone_flags, int trace);

ARGUMENTS

       child
	   new child task

       clone_flags

	   CLONE_* flags from clone/fork/vfork system call

       trace
	   return value from tracehook_prepare_clone

DESCRIPTION

       This is called immediately after adding child to its parent's children list. The trace value is that returned by tracehook_prepare_clone.

       Called with current's siglock and write_lock_irq(tasklist_lock) held.

Kernel Hackers Manual 2.6.					     July 2010						   TRACEHOOK_FINISH_CLO(9)

vfork(2)							System Calls Manual							  vfork(2)

Name
       vfork - spawn new process in a virtual memory-efficient way

Syntax
       pid = vfork()
       int pid;

Description
       The  can  be used to create new processes without fully copying the address space of the old process, which is inefficient in a paged envi-
       ronment.  It is useful when the purpose of would have been to create a new system context for an The system call differs from in  that  the
       child borrows the parent's memory and thread of control until a call to or an exit (either by a call to or abnormally.)	The parent process
       is suspended while the child is using its resources.

       The system call returns a value of zero (0) in the child's context and, later, the pid of the child in the parent's context.

       The system call can normally be used just like It does not work, however, to return while running in the childs context from the  procedure
       which  called because the eventual return from would then return to a nonexistent stack frame.  Be careful, also, to call _exit rather than
       exit if you cannot call because exit will flush and close standard I/O channels and thereby cause problems in the parent process's standard
       I/O data structures.  Even with it is wrong to call exit, because buffered data would then be flushed twice.

Restrictions
       To avoid a possible deadlock situation, processes which are children in the middle of a are never sent SIGTTOU or SIGTTIN signals.  Rather,
       output or ioctls are allowed, and input attempts result in an end-of-file indication.

Diagnostics
       Same as for

See Also
       execve(2), fork(2), sigvec(2), wait(2)

																	  vfork(2)