| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
| |
No extra changes, just a newer Docker container to minimize noise in the
following commits.
|
| |
|
|
| |
Disable rust by default for all instance, only enabling it where it's specified.
|
| |
|
|
| |
Use v6.18-rc1 and the latest linux-next tag.
|
| | |
|
| |
|
|
|
|
|
|
| |
To get coverage of PREEMPT_RT as well.
The disabled configs are marked as incompatible
with PREEMPT_RT in Kconfig files.
Fixes #6225
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add comedi.yml fragment with all usb and manually configurable
legacy comedi drivers. Specify x86_64-only setting for drivers
that depend on CONFIG_ISA[_BUS].
- Set the comedi.comedi_num_legacy_minors=4 kernel config param.
That way there are always /dev/comediN devices to try
COMEDI_DEFCONFIG ioctl on.
- Enable comedi.yml fragment for most instances.
Disable it for ChromeOS and Android, as well as some other arches
to avoid conflicts.
This change will disable some already set COMEDI config options (like
COMEDI usb drivers) in a few instances. It should not adversely affect
overall coverage as most other instances will keep those options and
add more on top.
|
| |
|
|
| |
Use v6.16-rc1 and the latest linux-next tag.
|
| |
|
|
| |
Enable RUST as well as other Rust-related configs.
|
| |
|
|
| |
The bugs that were popping up during image tests now seem to be fixed.
|
| | |
|
| |
|
|
| |
Use the latest linux-next and torvalds releases.
|
| | |
|
| |
|
|
|
| |
It will be available from v6.15, but we can already enable it for
linux-next.
|
| |
|
|
| |
Use the latest linux-next and the latest torvalds release.
|
| |
|
|
|
| |
Here we go again, now a different bug:
https://syzkaller.appspot.com/bug?extid=72b65b56208e052e606c
|
| |
|
|
|
|
| |
It is now resolved on torvalds and linux-next.
Fixes #5828.
|
| |
|
|
|
| |
It must have been fixed since Linux 5.18 and Clang 13.
See #5773.
|
| |
|
|
|
| |
It's currently broken even in torvalds, so if we don't disable it for
some time we risk not updating all kernel images for several more weeks.
|
| |
|
|
|
| |
Remove the deprecated options.
Replace old "linux-next" conditions with the version numbers.
|
| |
|
|
| |
Enabled CONFIG_SMB_SERVER.
|
| |
|
|
|
|
|
|
| |
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/
|
| | |
|
| |
|
|
|
| |
The kernel is not able to pass the test at the moment. See:
https://lore.kernel.org/all/66eb52dc.050a0220.92ef1.0006.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.
|
| |
|
|
| |
To enable new USB drivers from the distro configs added in the last patch.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Disable unmaintained code parts (at least those known so far) in
existing configs and enable them in a special upstream-unmaintained.config
file.
|
| |
|
|
|
| |
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.
|
| |
|
|
| |
Closes #3918.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
It seems we can cover them in qemu.
|
| | |
|
| |
|
|
| |
Technologies we want to use and test if available.
|
| | |
|
| | |
|
| |
|
|
| |
Currently syzbot is unable to symbolize reports for DWARF5.
|
| | |
|
| |
|
|
|
|
|
| |
Update the configs to the latest Linux versions: v6.2-rc5 and
next-20230124.
Enable CONFIG_NMI_CHECK_CPU and rcupdate.rcu_cpu_stall_cputime.
|
| |
|
|
|
|
| |
Enable write support for UFS. The description says experimental/dangerous,
but seems to mean only that images can be corrupted
("you should back up your UFS partitions beforehand").
|