go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/pkg/seccomp
History
Fabricio Voznika eaac94d91c Use RET_KILL_PROCESS if available in kernel 
RET_KILL_THREAD doesn't work well for Go because it will
kill only the offending thread and leave the process hanging.
RET_TRAP can be masked out and it's not guaranteed to kill
the process. RET_KILL_PROCESS is available since 4.14.

For older kernel, continue to use RET_TRAP as this is the
best option (likely to kill process, easy to debug).

PiperOrigin-RevId: 222357867
Change-Id: Icc1d7d731274b16c2125b7a1ba4f7883fbdb2cbd
 		2018-11-20 22:56:51 -08:00
..
BUILD Track paths and provide a rename hook. 2018-10-23 00:20:15 -07:00
seccomp.go Use RET_KILL_PROCESS if available in kernel 2018-11-20 22:56:51 -08:00
seccomp_rules.go Use correct company name in copyright header 2018-10-19 16:35:11 -07:00
seccomp_test.go Use RET_KILL_PROCESS if available in kernel 2018-11-20 22:56:51 -08:00
seccomp_test_victim.go Use RET_KILL_PROCESS if available in kernel 2018-11-20 22:56:51 -08:00
seccomp_unsafe.go Use RET_KILL_PROCESS if available in kernel 2018-11-20 22:56:51 -08:00