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

	Commit message (Collapse)	Author	Age	Files	Lines
*	dashboard/config/linux: regenerate	Taras Madan	2026-01-20	1	-39/+54
\|
*	dashboard/config: regenerate Linux configs	Aleksandr Nogikh	2026-01-15	1	-6/+14
\| \| \| \| \|	No extra changes, just a newer Docker container to minimize noise in the following commits.
*	dashboard: regenerate Linux configs	Pimyn Girgis	2025-10-20	1	-4/+10
\| \| \| \|	Use v6.18-rc1 and the latest linux-next tag.
*	dashboard/config/linux: regenerate files	Taras Madan	2025-10-06	1	-54/+83
\|
*	dashboard/config/linux: always enable GVNIC	Aleksandr Nogikh	2025-08-08	1	-1/+6
\|
*	dashboard/config/linux: disable CONFIG_CGROUP_BPF	Aleksandr Nogikh	2025-07-17	1	-3/+3
\| \| \| \| \| \| \| \| \| \|	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: regenerate Linux configs	Aleksandr Nogikh	2025-06-13	1	-31/+34
\| \| \| \|	Use v6.16-rc1 and the latest linux-next tag.
*	dashboard/config/linux: add upstream-rust-kasan config	Aleksandr Nogikh	2025-05-20	1	-5/+9
\| \| \| \|	Enable RUST as well as other Rust-related configs.
*	dashboard/config: enable ANDROID_BINDERFS	Aleksandr Nogikh	2025-04-29	1	-3/+3
\| \| \| \|	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	-15/+26
\| \| \| \|	Use the latest linux-next and torvalds releases.
*	dashboard/config: regenerate Linux configs	Aleksandr Nogikh	2025-03-29	1	-60/+85
\| \| \| \|	Use the latest linux-next and the latest torvalds release.
*	dashboard/config/linux: enable FORTIFY_SOURCE for clang	Aleksandr Nogikh	2025-02-13	1	-2/+1
\| \| \| \| \|	It must have been fixed since Linux 5.18 and Clang 13. See #5773.
*	dashboard/config/linux: update to v6.13 and latest next	Aleksandr Nogikh	2025-01-30	1	-65/+82
\| \| \| \| \|	Remove the deprecated options. Replace old "linux-next" conditions with the version numbers.
*	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: regenerate configs	Dmitry Vyukov	2024-08-30	1	-2/+2
\| \| \| \|	Regenerate deterministic configs.
*	dashboard/config: regenerate Linux configs	Aleksandr Nogikh	2024-08-29	1	-37/+75
\| \| \| \| \|	Regenerate the configs using the latest mainline, linux-next and stable versions.
*	dashboard/config: regenerate configs	Andrey Konovalov	2024-07-25	1	-15/+6
\| \| \| \|	To enable new USB drivers from the distro configs added in the last patch.
*	dashboard/config: add -next configs for KMSAN	Alexander Potapenko	2024-07-18	1	-0/+4919
	We are going to replace ci-upstream-kmsan-gce-386-root with an x86_64 instance tracking -next. The new configs will be using smack instead of AppArmor to increase the overall KMSAN coverage.