diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/pseudo_syscalls.md | 22 |
1 files changed, 3 insertions, 19 deletions
diff --git a/docs/pseudo_syscalls.md b/docs/pseudo_syscalls.md index c5df49ef1..cb899e6fc 100644 --- a/docs/pseudo_syscalls.md +++ b/docs/pseudo_syscalls.md @@ -23,25 +23,9 @@ amount of code, possibility of extending syzlang to cover this case, etc). First, think about the scope of the pseudo-syscall and which systems and subsystems it will be related to. The executor includes a fixed set of C -header files containing the code of the pseudo-syscalls. Check if the -new one can fit in one of the existing files before creating a new -one. These header files are defined in [gen.go](../pkg/csource/gen.go): - - executorFilenames := []string{ - "common_linux.h", - "common_bsd.h", - "common_fuchsia.h", - "common_windows.h", - "common_test.h", - "common_kvm_amd64.h", - "common_kvm_arm64.h", - "common_usb_linux.h", - "common_usb_netbsd.h", - "common_usb.h", - "android/android_seccomp.h", - "kvm.h", - "kvm_amd64.S.h", - } +header files `executor/common*.h` containing the code of the pseudo-syscalls. +Check if the new one can fit in one of the existing files before creating +a new one. For instance, if our new pseudo-syscall is Linux-specific, then [common_linux.h](../executor/common_linux.h) would be the place to put it. |