| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
No extra changes, just a newer Docker container to minimize noise in the
following commits.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
To enable new USB drivers from the distro configs added in the last patch.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Bump the Android kernels to their latest SHAs and generate
the kernel configs using tools/syz-env.
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit d341bdbd6837aa0214ee9dfd1c3ddfc58c2a0c9c.
The bump of CONFIG_FRAME_WARN was done for Android 5.10 with the hope
to get rid of the -Wframe-larger-than errors that were hit when
KASAN_STACK && CC_IS_CLANG were set. Unfortunately this didn't fix the
build as the stack instrumentation when using clang is broken and the
errors were hit again as we can't predict the increase of the stack. The
fix is to disable CONFIG_WERROR which now is done because we just bumped
the Android 5.10 kernel config (which contains CONFIG_WERROR=y) and the
kernel config tweak that disables CONFIG_WERROR now does its job
(see dashboard/config/linux/bits/base.yml).
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
|
| |
|
|
|
|
| |
Update configs to latest android13-5.15-lts.
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
|
| |
|
|
|
| |
We are not able to build Android 5.10 because of that warning for
already more than 100 days. Just in case bump it for all Androids.
|
| | |
|
| |
|
|
|
|
|
| |
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 some new configs that are reachable in VMs
and some new debugging configs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update linux upstream configs to the latest mainline/linux-next tags.
- RANDOM_TRUST_CPU was removed (defaults to y)
- RANDOM_TRUST_BOOTLOADER was removed (defaults to y)
- X86_SGX now requires X86_X2APIC
- DRM_VMWGFX_FBCON was removed
- ANDROID was removed
- NFT_OBJREF was removed
- CAN_SLCAN now requires new CAN_NETLINK
- CRYPTO_BLAKE2S was split into CRYPTO_BLAKE2S_X86 and CRYPTO_BLAKE2S_ARM
- DEBUG_VM_VMACACHE was removed
- CONTEXT_TRACKING_FORCE was removed
- DRM_DP_AUX_CHARDEV now requires DRM_I915 (or some other DRM driver)
- CRYPTO_SM4 was split into x86_64 amd arm64 configs
- ARM_CRYPTO was removed
- BINFMT_SHARED_FLAT was removed
Also update all configs that were marked as linux-next.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Background:
- syz-kconf loads and overlays config fragments to form a final kernel
config. Fragments are loaded top to bottom as defined in the includes
section of main.yml or your downstream syz-kconf config.
- A config fragment loaded later can override kconf options set by an
earlier loaded fragment. However the override keyword can only be used
if an earlier fragment really did set the same option. Otherweise an
error is raised.
- With this in mind it makes sense to load fragments from broadest scope
to most specific e.g. base -> x86_64 -> chromeos, so that chromeos can
override a setting usually enabled on x86_64 machines.
The Problem:
- Before this change shell snippets were executed in order they were
loaded from the fragments.
- This is unfortunate as the broad fragments like x86_64.yml expect to
operate on an existing .config with their shell snippets. Meanwhile
some downstream distros like icebreaker generate their config using
such a shell snippet.
- Hence ordering the fragments like base -> x86_64 -> icebreaker results
in an error about the x86_64 not finding a .config without this
change. Meanwhile ordering icebreaker -> base -> x86_64 works, but
means the icebreaker fragment can't override x86_64 kconf options.
The Solution:
- This change resolves the problem outlined above by reversing the order
shell snippets are executed. Now shell snippets will be executed
starting with the most recently loaded fragment. This way the proposed
fragment order base -> x86_64 -> icebreaker becomes viable.
- Luckily the shell section isn't heavily used, so this change didn't
result in meaningfull final config changes.
|
| |
|
|
|
|
| |
Updated android-5.15 configs with syz-kconfig auto-generated files.
Signed-off-by: Tadeusz Struk <tadeusz.struk@linaro.org>
|
|
|
The tag that is provided is from 'android13-5.15-lts'.
The LTS version must be used, as it is more up-to-date in terms of
security fixes and stable back-ports than its non-lts counterpart.
Using a tag from the non-lts branch will result in lots of false
positives which would end up wasting quality engineering time.
Signed-off-by: Tadeusz Struk <tadeusz.struk@linaro.org>
|
