Home
last modified time | relevance | path

Searched refs:PTRACE_ATTACH (Results 1 – 6 of 6) sorted by relevance

/linux-4.1.27/Documentation/security/
DYama.txt40 other process (and its descendants) are allowed to call PTRACE_ATTACH
51 0 - classic ptrace permissions: a process can PTRACE_ATTACH to any other
58 with the inferior it wants to call PTRACE_ATTACH on. By default,
62 an allowed debugger PID to call PTRACE_ATTACH on the inferior.
66 with PTRACE_ATTACH, or through children calling PTRACE_TRACEME.
68 3 - no attach: no processes may use ptrace with PTRACE_ATTACH nor via
DSmack.txt218 object. For the PTRACE_ATTACH a read-write access is required.
219 1 - exact: this is the policy that limits PTRACE_ATTACH. Attach is
/linux-4.1.27/include/uapi/linux/
Dptrace.h21 #define PTRACE_ATTACH 16 macro
/linux-4.1.27/tools/testing/selftests/ptrace/
Dpeeksiginfo.c187 if (sys_ptrace(PTRACE_ATTACH, child, NULL, NULL) == -1) in main()
/linux-4.1.27/kernel/
Dptrace.c392 proc_ptrace_connector(task, PTRACE_ATTACH); in ptrace_attach()
1074 if (request == PTRACE_ATTACH || request == PTRACE_SEIZE) { in SYSCALL_DEFINE4()
1218 if (request == PTRACE_ATTACH || request == PTRACE_SEIZE) { in COMPAT_SYSCALL_DEFINE4()
/linux-4.1.27/drivers/connector/
Dcn_proc.c205 if (ptrace_id == PTRACE_ATTACH) { in proc_ptrace_connector()