aboutsummaryrefslogtreecommitdiffstats
path: root/extract.sh
Commit message (Collapse)AuthorAgeFilesLines
* sys/syz-extract: move from syz-extractDmitry Vyukov2017-06-171-69/+0
|
* sys: add basic AF_LLC sockets descriptionsAndrey Konovalov2017-05-291-1/+1
|
* sys: add syscall description for /dev/ion.Billy Lau2017-04-251-1/+1
|
* sys: move ipv6 sockets to its own fileAndrey Konovalov2017-04-071-2/+3
|
* sys: add basic AF_AX25 descriptionsAndrey Konovalov2017-03-311-1/+1
|
* sys: add basic AF_IPX descriptionsAndrey Konovalov2017-03-311-1/+2
|
* sys: add dccp socket & packet descriptionsAndrey Konovalov2017-02-131-7/+7
|
* sys: split socket.txt into multiple files based on socket typeAndrey Konovalov2017-02-091-8/+11
| | | | | This just moves syscall descriptions and fixes up includes without any semantic changes.
* sys: add /dev/loop descriptionDmitry Vyukov2017-02-031-1/+1
|
* sys: move ipc syscalls into separate fileDmitry Vyukov2017-01-281-1/+1
|
* sys: drop kdbus descriptionDmitry Vyukov2017-01-181-1/+1
| | | | kdbus haven't been merged into mainline, unmaintained and seems to be replaced by bus1.
* executor: emit ethernet trafficAndrey Konovalov2016-11-291-1/+2
|
* extract.sh: allow generating constants for Android devices.Alexander Potapenko2016-09-051-7/+26
| | | | | | | To generate Android-specific constants run extract.sh with ANDROID=/path/to/kernel/checkout instead of LINUX=... Also remove /usr/bin from `make defconfig` invocations to let the user supply custom CC.
* extract.sh: add a comment with required package namesDmitry Vyukov2016-08-261-0/+3
|
* overhaul syscall description generation processDmitry Vyukov2016-08-261-0/+41
This splits generation process into two phases: 1. Extract values of constants from linux kernel sources. 2. Generate Go code. Constant values are checked in. The advantage is that the second phase is now completely independent from linux source files, kernel version, presence of headers for particular drivers, etc. This allows to change what Go code we generate any time without access to all kernel headers (which in future won't be limited to only upstream headers). Constant extraction process does require proper kernel sources, but this can be done only once by the person who added the driver and has access to the required sources. Then the constant values are checked in for others to use. Consant extraction process is per-file/per-arch. That is, if I am adding a driver that is not present upstream and that works only on a single arch, I will check in constants only for that driver and for that arch.