Searched refs:execve (Results 1 – 25 of 51) sorted by relevance
123
| /linux-6.1.9/tools/testing/selftests/exec/ |
| D | null-argv.c | 71 FORK(execve(argv[0], str, NULL)); in main()
72 FORK(execve(argv[0], NULL, NULL)); in main()
73 FORK(execve(argv[0], NULL, envp)); in main()
74 FORK(execve(argv[0], args, NULL)); in main()
75 FORK(execve(argv[0], args, envp)); in main()
|
| D | recursion-depth.c | 61 int rv = execve(FILENAME, NULL, NULL); in main()
|
| /linux-6.1.9/Documentation/userspace-api/ |
| D | no_new_privs.rst | 5 The execve system call can grant a newly-started program privileges that
23 execution environment in a manner that persists across execve. Any task
25 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 setgid
30 execve.
42 involve ``execve()``. An appropriately privileged task can still call
48 execve and can change the behavior of newly-executed programs.
|
| D | spec_ctrl.rst | 43 cleared on :manpage:`execve(2)`.
|
| /linux-6.1.9/Documentation/arm64/ |
| D | asymmetric-32bit.rst | 19 ``execve(2)`` of 32-bit ELF binaries, with the latter returning
65 ``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 will
94 policy or cpuset hierarchy, in which case the ``execve(2)`` continues
100 ``execve(2)`` is invalidated.
110 ``execve(2)`` of a 32-bit program from a 64-bit deadline task will
114 `execve(2)`_, in which case step (1) is skipped and a warning is
136 (2) of the process described in `execve(2)`_ and the cpuset hierarchy is
|
| D | sme.rst | 106 exceptions for execve() described in section 6.
172 Inherit the current vector length across execve(). Otherwise, the
173 vector length is reset to the system default at execve(). (See
178 Defer the requested vector length change until the next execve()
182 call immediately after the next execve() (if any) by the thread:
201 to be applied at the next execve() by the thread (dependent on whether
214 vector length that will be applied at the next execve() by the calling
238 Vector length will be inherited across execve().
242 fork() or vfork() and the corresponding execve() in typical use).
361 * At every execve() call, the new vector length of the new process is set to
[all …]
|
| D | sve.rst | 127 exceptions for execve() described in section 6.
216 Inherit the current vector length across execve(). Otherwise, the
217 vector length is reset to the system default at execve(). (See
222 Defer the requested vector length change until the next execve()
226 call immediately after the next execve() (if any) by the thread:
246 to be applied at the next execve() by the thread (dependent on whether
259 vector length that will be applied at the next execve() by the calling
277 Vector length will be inherited across execve().
281 fork() or vfork() and the corresponding execve() in typical use).
443 * At every execve() call, the new vector length of the new process is set to
[all …]
|
| /linux-6.1.9/tools/perf/trace/strace/groups/ |
| D | file | 4 execve
|
| D | string | 10 execve
|
| /linux-6.1.9/tools/testing/selftests/timens/ |
| D | exec.c | 80 execve("/proc/self/exe", cargv, cenv); in main()
|
| /linux-6.1.9/tools/testing/selftests/rlimits/ |
| D | rlimits-per-userns.c | 81 execve(service_prog, argv, envp); in fork_child()
|
| /linux-6.1.9/tools/testing/selftests/powerpc/benchmarks/ |
| D | fork.c | 79 if (execve("./exec_target", argv, NULL) == -1) { in run_exec()
|
| /linux-6.1.9/Documentation/security/ |
| D | credentials.rst | 167 ``execve()``.
170 ``execve()``, especially when a binary is executed that will execute as
177 execve(). They aren't used directly as objective or subjective
242 operations allowed or disallowed as a result. In the case of execve(), the
446 ``execve()``.
|
| /linux-6.1.9/kernel/ |
| D | audit.h | 200 } execve; member
|
| /linux-6.1.9/tools/perf/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 70 59 64 execve sys_execve
390 520 x32 execve compat_sys_execve
|
| /linux-6.1.9/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 70 59 64 execve sys_execve
390 520 x32 execve compat_sys_execve
|
| /linux-6.1.9/arch/sparc/kernel/syscalls/ |
| D | syscall.tbl | 82 59 32 execve sys_execve sys32_execve
83 59 64 execve sys64_execve
|
| /linux-6.1.9/Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 8 call and the execve() system call. From the kernel's point of view, execve()
|
| /linux-6.1.9/tools/perf/arch/mips/entry/syscalls/ |
| D | syscall_n64.tbl | 67 57 n64 execve sys_execve
|
| /linux-6.1.9/arch/mips/kernel/syscalls/ |
| D | syscall_n64.tbl | 67 57 n64 execve sys_execve
|
| D | syscall_n32.tbl | 67 57 n32 execve compat_sys_execve
|
| /linux-6.1.9/arch/ia64/kernel/syscalls/ |
| D | syscall.tbl | 21 9 common execve ia64_execve
|
| /linux-6.1.9/Documentation/process/ |
| D | adding-syscalls.rst | 119 ``execve()`` in another thread could leak a descriptor to
400 (``fork``/``vfork``/``clone``) or even architecture (``execve``/``execveat``)
448 file open (``open``/``openat``), program execution (``execve``/``exeveat``) or
|
| /linux-6.1.9/arch/xtensa/kernel/syscalls/ |
| D | syscall.tbl | 131 117 common execve sys_execve
|
| /linux-6.1.9/Documentation/security/keys/ |
| D | request-key.rst | 128 /sbin/request-key at the appropriate places because (a) execve will discard two
|
123