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

	Commit message (Collapse)	Author	Age	Files	Lines
*	dashboard/config: regenerate Linux configs	Aleksandr Nogikh	2026-01-15	1	-4/+4
\| \| \| \| \|	No extra changes, just a newer Docker container to minimize noise in the following commits.
*	dashboard/config/linux: regenerate files	Taras Madan	2025-10-06	1	-1/+1
\|
*	dashboard/config/linux: always enable GVNIC	Aleksandr Nogikh	2025-08-08	1	-1/+1
\|
*	dashboard/config/linux: disable CONFIG_CGROUP_BPF	Aleksandr Nogikh	2025-07-17	1	-4/+4
\| \| \| \| \| \| \| \| \| \|	It seems incredibly difficult to clean up the side effects of this kernel functionality. Keep it enabled only on a new config dedicated specifically for the snapshot-based instance. Closes #5956.
*	dashboard/config/linux: add upstream-rust-kasan config	Aleksandr Nogikh	2025-05-20	1	-4/+6
\| \| \| \|	Enable RUST as well as other Rust-related configs.
*	dashboard/config: enable ANDROID_BINDERFS	Aleksandr Nogikh	2025-04-29	1	-4/+4
\| \| \| \|	The bugs that were popping up during image tests now seem to be fixed.
*	dashboard/configs: regenerate Linux configs	Aleksandr Nogikh	2025-04-25	1	-9/+11
\| \| \| \|	Use the latest linux-next and torvalds releases.
*	dashboard/config: regenerate clang configs with LLVM=1	Aleksandr Nogikh	2025-04-17	1	-5/+3
\|
*	dashboard/config: set RCU_EXP_CPU_STALL_TIMEOUT to 0	Aleksandr Nogikh	2024-11-01	1	-1/+1
\| \| \| \| \| \| \| \|	The zero values makes the kernel use the RCU_CPU_STALL_TIMEOUT value, which is already set to a big enough value. Context: see the recent LKML discussion at https://lore.kernel.org/all/6723aa4d.050a0220.35b515.0161.GAE@google.com/T/
*	dashboard/config/linux: increase number of devices to 32	Dmitry Vyukov	2024-10-24	1	-1/+1
\|
*	dashboard/config/linux: bump lockdep consts even more	Dmitry Vyukov	2024-08-30	1	-2/+2
\| \| \| \| \|	Btrfs needs higher values to avoid false positives: https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/
*	dashboard/config: disable CONFIG_FRAME_WARN on ChromeOS	Aleksandr Nogikh	2024-05-07	1	-1/+1
\| \| \| \|	As suggested by @groeck.
*	dashboard/config: update ChromeOS configs	Aleksandr Nogikh	2024-05-03	1	-0/+8243
	Use the latest revisions for existing configs. Add the new ChromeOS 6.6 config. No longer generate ChromeOS 5.4 configs. Switch ChromeOS configs to clang.