| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
| |
No extra changes, just a newer Docker container to minimize noise in the
following commits.
|
| |
|
|
| |
Use v6.18-rc1 and the latest linux-next tag.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Use v6.16-rc1 and the latest linux-next tag.
|
| |
|
|
| |
Enable RUST as well as other Rust-related configs.
|
| |
|
|
| |
Use the latest linux-next and torvalds releases.
|
| |
|
|
| |
Use the latest linux-next and the latest torvalds release.
|
| |
|
|
|
| |
Remove the deprecated options.
Replace old "linux-next" conditions with the version numbers.
|
| |
|
|
|
|
|
|
| |
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/
|
| | |
|
| |
|
|
|
| |
Btrfs needs higher values to avoid false positives:
https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/
|
| |
|
|
| |
Regenerate deterministic configs.
|
| |
|
|
|
| |
Regenerate the configs using the latest mainline, linux-next and stable
versions.
|
| |
|
|
|
| |
It's not the default for most kernels, so it makes sense to test it more.
E.g. for KCSAN, KMSAN we have only 1 instance, makes sense to test LRU_GEN.
|
| |
|
|
|
| |
Regenerate the configs using the latest RC and the latest linux-next
tag.
|
| |
|
|
|
|
| |
Regenerate configs using latest Linux release candidate and linux-next.
Enable more bcachefs configs.
|
| |
|
|
| |
Regenerate the configs using the latest Linux revisions.
|
| |
|
|
|
|
|
| |
This has become possible with the new series from Jan Kara:
https://lore.kernel.org/all/20231101173542.23597-1-jack@suse.cz/
Regenerate configs on the latest linux-next.
|
| |
|
|
|
|
|
|
|
| |
Use latest Linux mainline and -next versions.
Disable config options that were dropped.
Stop disabling PINCTRL for arm64_emu -- it's too tricky to ensure it's
not enabled + it's only possible to test it on qemu anyway.
|
| |
|
|
|
| |
1) Migration to a new Docker image changed toolchain versions.
2) Regenerate cuttlefish configs that were previously omitted.
|
| |
|
|
| |
This will let users boot directly from the vmlinux file.
|
| |
|
|
| |
Disable more kernel configs for baseline files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Update mainline tag and linux-next version.
Notable changes:
- SLAB is being deprecated. To still be able to test it we need
to set SLAB_DEPRECATED.
Due to SLAB deprecation, the kcsan and leak instances are switched to
SLUB to avoid tripping over issues due to SLAB not being supported
properly anymore.
|
|
|
Introduce a variant of upstream-apparmor-kasan, which enables:
- kasan.fault=panic_on_write [1]
- kasan_multi_shot, so that panic_on_warn does cause KASAN to
panic on bad non-write accesses
As discussed in [1], "KASAN reported invalid _writes_ are of special
interest, because they have greater potential to corrupt random kernel
memory or be more easily exploited."
With this config we can set up a syzbot instance that can detect such
issues.
[1] https://lore.kernel.org/linux-mm/20230614095158.1133673-1-elver@google.com/
|