Searched refs:interpreters (Results 1 – 4 of 4) sorted by relevance
| /linux/Documentation/userspace-api/ |
| H A D | check_exec.rst | 10 are intended for script interpreters and dynamic linkers to enforce a
18 syscalls and access arbitrary files. Such interpreters should then be
23 Script interpreters or dynamic linkers built for tailored execution environments
28 for script interpreters and dynamic linkers to check the securebits at run time
81 However, script interpreters may still use user configuration such as
95 For instance, script interpreters called with a script snippet as argument
|
| /linux/Documentation/admin-guide/ |
| H A D | binfmt-misc.rst | 119 binds interpreters needs; see the bpf section below. The flag
134 - the amount of pre-opened interpreters by ``F``, or bound to a ``B`` entry
211 An entry can instead bind the interpreters its handler may use, so that no
226 binds at most 100 interpreters, and each one is charged against
237 Enabling the entry ends this. Its interpreters are read at exec time with
246 puts its interpreters. A name is a single word of printable ASCII, at most
298 the interpreters it binds already pre-open what ``F`` would. The
309 Transparent interpreters
378 ``C``, register only trusted interpreters. The substituted loader runs
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | ipe.rst | 95 to the interpreter. This is because the way interpreters execute these
100 interpreters can use it to signal the kernel that a script file will be executed,
110 to take the initiative, and existing interpreters won't be automatically
|
| /linux/kernel/bpf/ |
| H A D | core.c | 2464 static unsigned int (*interpreters[])(const void *ctx, variable
2625 if (idx < ARRAY_SIZE(interpreters)) { in bpf_prog_select_interpreter()
2626 fp->bpf_func = interpreters[idx]; in bpf_prog_select_interpreter()
|