bsd/kern/kern_exec.c

100 #include <sys/exec.h>
174 /* support for child creation in exec after vfork */
623 				 * For vfork exec, the current implementation has not set up the thread in the
909 	 * requested them on exec.
939 	 * Close file descriptors which specify close-on-exec.
952 	 * deal with voucher on exec-calling thread.
1047 	 * Otherwise, use the name passed into exec.
1268 	/* Use imgp->ip_strings, which contains the copyin-ed exec path */
1269 	DTRACE_PROC1(exec, uintptr_t, imgp->ip_strings);
1382 	 * Call out to allow 3rd party notification of exec.
1710 			 * ensure it's -not- marked as close-on-exec.
1753 	 * this spawn only) as if "close on exec" is the default
1884  *		uap->fname		File name to exec
2114 		imgp->ip_flags |= IMGPF_SPAWN;	/* spawn w/o exec */
2291 		/* process completed the exec */
2314 		 * we leave them, since we are in the exec case instead.
2428 		/* then flag exec has occurred */
2443 	 * This must be done after the exec so that the child's thread is ready,
2525 		 * did vfork(2) then exec(2).  Thus the proc::: probes
2526 		 * are very fork/exec oriented.  The details of this
2538 			 * /usr/bin, rely on the the 'exec-success'
2545 			 * so 'exec-success' fires on it as it leaves
2618  * Parameters:	uap->fname		File name to exec
2657  * Parameters:	uap->fname		File name to exec
3154 		/* imgp->ip_argspace--; not counted towards exec args total */
3593  * exec'ing a non-SUGID image, then  this is the point of no return.
3635 	 *		slow down the exec fast path for normal binaries.
3755 			 * a setuid exec to be able to access/control the
3856 	 * the saved user and group in exec'ed programs.
4054 	panic("Process 1 exec of %s failed, errno %d", init_program_name, error);
4416 	 * approve of exec, kill and return immediately.
4440 	 * and the exec should continue, KERN_FAILURE if the exec should