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

	Commit message (Collapse)	Author	Age	Files	Lines
*	all: remove loop variables scoping	Taras Madan	2025-02-17	1	-1/+0
\|
*	prog: make TestRotationCoverage faster	Florent Revest	2024-12-19	1	-1/+1
\| \| \| \| \| \|	Now that we added automatically generated syscalls to the Linux corpus, we added a lot of work to the TestRotationCoverage test. We can make it faster by skipping all automatically generated syscalls.
*	prog: fix episodic failures to generate a call	Dmitry Vyukov	2024-05-08	1	-0/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Tests sometimes fail as: --- FAIL: TestCreateResourceRotation (0.97s) ... resources_test.go:181: testing call syz_io_uring_submit resources_test.go:187: failed to create resource fd_dir FAIL Almost always it's related to fd_dir resource. The problem is with no_generate syscalls (we have lots of no_generate mount syscalls that produce fd_dif). Rotator considers them as legit resource ctors, but the actual code in createResource does not. As the result Rotator creates subsets of syscalls where not all resources can be created. The same problem affects TransitivelyEnabledCalls. It may leave syscalls that require resources produced only by no_generate syscalls. We won't be able to produce such resources during fuzzing. Split Syscall.outputResources to createResources (can actually be used to create, excludes no_generate) and usesResources, this includes no_generate syscalls.
*	prog: make TestRotationCoverage test more robust	Dmitry Vyukov	2022-08-11	1	-1/+8
\| \| \| \| \| \| \| \| \|	Currently we do 2e3 iterations or rotation and test that we selected each syscall at least once. This both takes lots of time and results in episodic flakes. Loop 1e4 iterations or until we selected each syscall at least once. This will result it fewer flakes and also may be faster in common case.
*	prog: fix Rotator determinism	Dmitry Vyukov	2022-08-11	1	-0/+16
\| \| \| \| \|	Currently Rotator.Select produces non-deterministic results because it relies on map iteration order. Fix that.
*	prog: fix oob panic in rotatorState.Select	Dmitry Vyukov	2021-01-05	1	-0/+13
\| \| \| \| \|	Reported-by: ManhNDd Fixes #2372
*	prog: increase number of itereations in TestRotationCoverage	Dmitry Vyukov	2020-06-05	1	-1/+1
\| \| \| \| \|	It failed on CI once: https://github.com/google/syzkaller/pull/1789/checks?check_run_id=740199305
*	prog: reduce size of -short tests	Dmitry Vyukov	2020-05-18	1	-1/+1
\| \| \| \|	Reduce size of tests that run for more than 1s in short mode.
*	syz-manager: corpus rotation	Dmitry Vyukov	2019-12-30	1	-0/+122
	Use a random subset of syscalls/corpus/coverage for each individual VM run. Hypothesis is that this should allow fuzzer to get more coverage find more bugs in saturated state (stuck in local optimum). See the issue and comments for details. Update #1348