diff options
| author | Andrey Konovalov <andreyknvl@google.com> | 2020-06-12 14:48:32 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-12 14:48:32 +0200 |
| commit | df5902545c718f3a92f6423aae1f43d8144bd53c (patch) | |
| tree | 581c7b33e754356de4c8935ce410f6f123510e8d /docs | |
| parent | c149e34955491af9b97536f142dc6f547769130b (diff) | |
Update syscall_descriptions.md
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/syscall_descriptions.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/syscall_descriptions.md b/docs/syscall_descriptions.md index 78e46e832..77abbad79 100644 --- a/docs/syscall_descriptions.md +++ b/docs/syscall_descriptions.md @@ -57,11 +57,12 @@ To enable fuzzing of a new kernel interface: 1. Study the interface, find out which syscalls are required to use it. Sometimes there is nothing besides the source code, but here are some things that may help: - - Searching the Internet for the subsystem name and/or some unique constants. + - Searching the Internet for the interface name and/or some unique constants. - Grepping Documentation/ dir in the kernel. - Searching tools/testing/ dir in the kernel. - Looking for large comment blocks in the source code. - Finding commit that added the interface via `git blame` or `git log` and reading the commit description. + - Reading source code of or tracing libraries or applications that are known to use this interface. 2. Using [syntax documentation](syscall_descriptions_syntax.md) and [existing descriptions](/sys/linux/) as an example, add a declarative |