Searched refs:execve (Results 1 – 25 of 46) sorted by relevance
12
| /kernel/linux/build/test/kernel_ltp/syscalls/execve/ |
| D | BUILD.gn | 19 sources = [ "//third_party/ltp/testcases/kernel/syscalls/execve/execve01.c" ]
25 [ "//third_party/ltp/testcases/kernel/syscalls/execve/execve01_child.c" ]
30 sources = [ "//third_party/ltp/testcases/kernel/syscalls/execve/execve02.c" ]
35 sources = [ "//third_party/ltp/testcases/kernel/syscalls/execve/execve03.c" ]
40 sources = [ "//third_party/ltp/testcases/kernel/syscalls/execve/execve04.c" ]
45 sources = [ "//third_party/ltp/testcases/kernel/syscalls/execve/execve05.c" ]
51 [ "//third_party/ltp/testcases/kernel/syscalls/execve/execve_child.c" ]
|
| /kernel/linux/linux-5.10/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)`.
|
| /kernel/linux/build/test/kernel_ltp/syscalls/ |
| D | BUILD.gn | 163 "execve:execve01",
164 "execve:execve01_child",
165 "execve:execve02",
166 "execve:execve03",
167 "execve:execve04",
168 "execve:execve05",
|
| /kernel/liteos_a/apps/init/src/ |
| D | init.c | 63 (void)execve(samplePath, NULL, NULL); in main()
89 (void)execve(shellPath, NULL, NULL); in main()
|
| /kernel/linux/linux-5.10/tools/perf/trace/strace/groups/ |
| D | file | 4 execve
|
| D | string | 10 execve
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | sve.rst | 112 exceptions for execve() described in section 6.
191 Inherit the current vector length across execve(). Otherwise, the
192 vector length is reset to the system default at execve(). (See
197 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 whether
234 vector length that will be applied at the next execve() by the calling
252 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 …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/exec/ |
| D | recursion-depth.c | 61 int rv = execve(FILENAME, NULL, NULL); in main()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/timens/ |
| D | exec.c | 80 execve("/proc/self/exe", cargv, cenv); in main()
|
| /kernel/liteos_a/apps/perf/src/ |
| D | perf_stat.c | 141 (void)execve(cmd.path, cmd.params, NULL); in PerfStat()
|
| D | perf_record.c | 183 (void)execve(cmd.path, cmd.params, NULL); in PerfRecord()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/powerpc/benchmarks/ |
| D | fork.c | 79 if (execve("./exec_target", argv, NULL) == -1) { in run_exec()
|
| /kernel/linux/linux-5.10/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()``.
|
| /kernel/linux/linux-5.10/kernel/ |
| D | audit.h | 190 } execve; member
|
| /kernel/linux/linux-5.10/tools/perf/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 70 59 64 execve sys_execve
380 520 x32 execve compat_sys_execve
|
| /kernel/linux/linux-5.10/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 70 59 64 execve sys_execve
380 520 x32 execve compat_sys_execve
|
| /kernel/linux/linux-5.10/arch/sparc/kernel/syscalls/ |
| D | syscall.tbl | 82 59 32 execve sys_execve sys32_execve
83 59 64 execve sys64_execve
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 8 call and the execve() system call. From the kernel's point of view, execve()
|
| /kernel/liteos_a/apps/shell/src/ |
| D | shmsg.c | 378 ret = execve(cmdName, paramArray, NULL); in ChildExec()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/arch/ia64/kernel/syscalls/ |
| D | syscall.tbl | 21 9 common execve ia64_execve
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/security/keys/ |
| D | request-key.rst | 128 /sbin/request-key at the appropriate places because (a) execve will discard two
|
12