Searched refs:execve (Results 1 – 25 of 47) sorted by relevance
12
5 The execve system call can grant a newly-started program privileges that23 execution environment in a manner that persists across execve. Any task25 clone, and execve and cannot be unset. With ``no_new_privs`` set, ``execve()``27 been done without the execve call. For example, the setuid and setgid30 execve.42 involve ``execve()``. An appropriately privileged task can still call48 execve and can change the behavior of newly-executed programs.
43 cleared on :manpage:`execve(2)`.
19 ``execve(2)`` of 32-bit ELF binaries, with the latter returning65 ``execve(2)``69 ``execve(2)``. This is not always possible on an asymmetric system,77 preserved across ``execve(2)`` of 32-bit programs.90 A subsequent ``execve(2)`` of a 64-bit program by the 32-bit task will94 policy or cpuset hierarchy, in which case the ``execve(2)`` continues100 ``execve(2)`` is invalidated.110 ``execve(2)`` of a 32-bit program from a 64-bit deadline task will114 `execve(2)`_, in which case step (1) is skipped and a warning is136 (2) of the process described in `execve(2)`_ and the cpuset hierarchy is
112 exceptions for execve() described in section 6.191 Inherit the current vector length across execve(). Otherwise, the192 vector length is reset to the system default at execve(). (See197 Defer the requested vector length change until the next execve()201 call immediately after the next execve() (if any) by the thread:221 to be applied at the next execve() by the thread (dependent on whether234 vector length that will be applied at the next execve() by the calling252 Vector length will be inherited across execve().256 fork() or vfork() and the corresponding execve() in typical use).393 * At every execve() call, the new vector length of the new process is set to[all …]
4 execve
10 execve
61 int rv = execve(FILENAME, NULL, NULL); in main()
80 execve("/proc/self/exe", cargv, cenv); in main()
81 execve(service_prog, argv, envp); in fork_child()
79 if (execve("./exec_target", argv, NULL) == -1) { in run_exec()
167 ``execve()``.170 ``execve()``, especially when a binary is executed that will execute as177 execve(). They aren't used directly as objective or subjective242 operations allowed or disallowed as a result. In the case of execve(), the446 ``execve()``.
193 } execve; member
1058 audit_log_format(*ab, "argc=%d", context->execve.argc); in audit_log_execve_info()1187 } while (arg < context->execve.argc); in audit_log_execve_info()2350 context->execve.argc = bprm->argc; in __audit_bprm()
70 59 64 execve sys_execve388 520 x32 execve compat_sys_execve
82 59 32 execve sys_execve sys32_execve83 59 64 execve sys64_execve
8 call and the execve() system call. From the kernel's point of view, execve()
67 57 n64 execve sys_execve
67 57 n32 execve compat_sys_execve
21 9 common execve ia64_execve
119 ``execve()`` in another thread could leak a descriptor to400 (``fork``/``vfork``/``clone``) or even architecture (``execve``/``execveat``)448 file open (``open``/``openat``), program execution (``execve``/``exeveat``) or
131 117 common execve sys_execve
128 /sbin/request-key at the appropriate places because (a) execve will discard two
2063 SYSCALL_DEFINE3(execve, in SYSCALL_DEFINE3() argument2083 COMPAT_SYSCALL_DEFINE3(execve, const char __user *, filename, in COMPAT_SYSCALL_DEFINE3() argument
