syz - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	sys: move linux descriptions to sys/linux	Dmitry Vyukov	2017-09-15	1	-855/+0
\|
*	executor, fuzzer: change the way Syzkaller opens the KCOV device	Victor Chibotaru	2017-08-30	1	-0/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	We have implemented a new version of KCOV, which is able to dump comparison operands' data, obtained from Clang's instrumentation hooks __sanitizer_cov_trace_cmp[1248], __sanitizer_cov_trace_const_cmp[1248] and __sanitizer_cov_trace_switch. Current KCOV implementation can work in two modes: "Dump only the PCs" or "Dump only comparisons' data". Mode selection is done by the following series of calls: fd = open(KCOV_PATH, ...); // works as previous ioctl(fd, KCOV_INIT_TRACE, ...); // works as previous mmap(fd, ...); // works as previous ioctl(fd, KCOV_ENABLE, mode); // mode = KCOV_MODE_TRACE_CMP or mode = KCOV_MODE_TRACE_PC Note that this new interface is backwards compatible, as old KCOV devices will just return -EINVAL for the last ioctl. This way we can distinguish if the KCOV device is able to dump the comparisons. Main changes in this commit: 1. Fuzzer now checks at startup which type (new/old) of KCOV device is running. 2. Executor now receives an additional flag, which indicates if executor should read the comparisons data from KCOV. The flag works on per-call basis, so executor can collect PCs or Comps for each individual syscall.
*	sys: add some known xattr names	Dmitry Vyukov	2017-08-16	1	-14/+0
\| \| \| \| \| \|	Move xattr syscalls to own file and better describe xattr names. They usually have prefix+name structure and there are some known values.
*	sys: describe clone/execve calls	Dmitry Vyukov	2017-08-12	1	-0/+4
\| \| \| \| \|	Update #211 Update #310
*	sys: describe chroot/getcwd/chdir/fchdir	Dmitry Vyukov	2017-08-12	1	-0/+4
\| \| \| \|	Update #211
*	statx: generate constants for updated flags	Jess Frazelle	2017-06-08	1	-7/+5
\| \| \| \|	Signed-off-by: Jess Frazelle <acidburn@google.com>
*	sys: add statx syscall	Jess Frazelle	2017-06-02	1	-0/+22
\| \| \| \| \| \| \| \| \|	The statx syscall was added in Linux 4.11, check out the kernel documentation[1] for more information. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a528d35e8bfcc521d7cb70aaf03e1bd296c8493f Signed-off-by: Jess Frazelle <acidburn@google.com>
*	sys: refactor and improve SCTP socket descriptions	Andrey Konovalov	2017-05-26	1	-1/+1
\|
*	sys: remove UFFD_FEATURE_EVENT_EXIT const	Dmitry Vyukov	2017-03-08	1	-1/+0
\| \| \| \|	It is going to be removed from kernel.
*	sys: describe uffd api features	Dmitry Vyukov	2017-03-02	1	-0/+8
\|
*	sys: add more filesystems and mount flags	Dmitry Vyukov	2017-02-05	1	-0/+8
\|
*	sys: minor assorted improvements to descriptions	Dmitry Vyukov	2017-02-03	1	-0/+12
\|
*	sys: move ipc syscalls into separate file	Dmitry Vyukov	2017-01-28	1	-42/+0
\|
*	sys: detail kvm syscalls more	Dmitry Vyukov	2017-01-09	1	-0/+1
\|
*	sys: describe new pkey_* syscalls	Dmitry Vyukov	2016-12-16	1	-0/+8
\|
*	sys: add new bpf descriptions	Dmitry Vyukov	2016-11-28	1	-0/+1
\| \| \| \|	These were just added to net-next.
*	sys: resolve some old TODOs in descriptions	Dmitry Vyukov	2016-09-05	1	-0/+2
\|
*	overhaul syscall description generation process	Dmitry Vyukov	2016-08-26	1	-0/+840
	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.