Searched refs:vfork (Results 51 – 61 of 61) sorted by relevance
123
| /openbmc/bmcweb/ |
| H A D | .clang-tidy | 215 clang-analyzer-security.insecureAPI.vfork,
|
| /openbmc/dbus-sensors/ |
| H A D | .clang-tidy | 213 clang-analyzer-security.insecureAPI.vfork,
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | nommu-mmap.rst | 12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | sme.rst | 262 fork() or vfork() and the corresponding execve() in typical use).
|
| H A D | sve.rst | 282 fork() or vfork() and the corresponding execve() in typical use).
|
| /openbmc/linux/Documentation/security/keys/ |
| H A D | core.rst | 144 clone, fork, vfork or execve occurs. A new keyring is created only when
148 clone, fork, vfork unless CLONE_THREAD is supplied, in which case it is
152 The session-specific keyring is persistent across clone, fork, vfork and
|
| /openbmc/linux/Documentation/process/ |
| H A D | adding-syscalls.rst | 400 (``fork``/``vfork``/``clone``) or even architecture (``execve``/``execveat``)
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | adding-syscalls.rst | 447 la memoria in spazio utente (``fork``/``vfork``/``clone``) o perfino
|
| /openbmc/linux/Documentation/translations/sp_SP/process/ |
| H A D | adding-syscalls.rst | 443 cambiar el espacio de memoria (``fork``/``vfork``/``clone``) o incluso de
|
| /openbmc/linux/arch/parisc/kernel/ |
| H A D | entry.S | 1656 fork_like vfork
|
| /openbmc/qemu/linux-user/ |
| H A D | strace.list | 1644 { TARGET_NR_vfork, "vfork" , NULL, NULL, NULL },
|
123