| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
1. DEBUG_GENERIC_PT.
2. DEBUG_XARRAY.
3. PHY_GOOGLE_USB.
|
| |
|
|
| |
Closes #6595.
|
| | |
|
| |
|
|
|
|
| |
Use the latest available revision and disable ANDROID_BINDER_IPC - as of
now, it's no longer possible to compile in both C and Rust versions at
the same time.
|
| |
|
|
|
| |
No extra changes, just a newer Docker container to minimize noise in the
following commits.
|
| |
|
|
| |
Ext4 is necessary for normal boot, enable it unconditionally in base.
|
| |
|
|
| |
Disable rust by default for all instance, only enabling it where it's specified.
|
| |
|
|
| |
Use v6.18-rc1 and the latest linux-next tag.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
It allows to use `syz-env make configs ... INSTANCE=`.
Helps with #6391
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Now that Rust Binder has been merged into the tree, we can enable it.
|
| | |
|
| | |
|
| |
|
|
| |
We haven't been fuzzing it on syzbot for a very long time.
|
| |
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
A config bisection between our LTS and Android configs have pointed to
the SERIAL_8250_RUNTIME_UARTS option determining whether the kernel
will hang during boot in qemu.
Set SERIAL_8250_RUNTIME_UARTS=4 on our Android kernels to make them
bootable.
|
| | |
|
| |
|
|
| |
Use the latest linux-next and torvalds releases.
|
| | |
|
| |
|
|
| |
We don't use these on syzbot.
|
| | |
|
| |
|
|
|
| |
Maximum config that still builds/boots.
This is useful for descriptions/interface auto-extraction.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
| |
kexec, memory hotplug/remove and THP features depend on architecture
specific code, so let's exercise this for riscv.
|
| |
|
|
|
|
|
|
|
|
|
| |
KASAN_INLINE was fixed back in early 2023 in the riscv kernel, see
merge commit 2667e3673f70 ("Merge patch series "RISC-V kasan rework").
It happens that the riscv configuration was already using KASAN_INLINE
so this is simply a cleanup.
Since this is my first commit in syzkaller, I also added myself and
Rivos in the AUTHORS/CONTRIBUTORS files.
|
| |
|
|
|
| |
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/
|
| |
|
|
|
|
| |
It seems to have caused boot problems on ci-upstream-gce-arm64.
Reported-by: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
|
| |
|
|
|
| |
Btrfs needs higher values to avoid false positives:
https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/
|
| |
|
|
| |
Regenerate deterministic configs.
|