| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
Use v6.18-rc1 and the latest linux-next tag.
|
| | |
|
| |
|
|
| |
Use v6.16-rc1 and the latest linux-next tag.
|
| |
|
|
| |
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.
|
| |
|
|
|
| |
Regenerate the configs using the latest mainline, linux-next and stable
versions.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
1. Bump KMSAN version to v5.18-rc4
Also switch to using clang-kmsan provided by syz-env.
2. Bump Linux version to v5.18
3. Bump linux-next version to next-20220601
Also enable DEBUG_NET for linux-next
|
| |
|
|
| |
Along with small changes due to changed Kconfig variables.
|
| |
|
|
|
| |
update linux to v5.18-rc1
fix dependency update errors
update configs
|
| |
|
|
|
|
|
|
|
| |
Move CONFIG_AID_FOR_SYZBOT to verbatim since it has for some reason
disappeared from the linux-next tree.
Add CONFIG_RCU_EXP_CPU_STALL_TIMEOUT and set it to the maximum value.
Otherwise it overwhelms syzbot with `INFO: rcu_preempt detected
expedited stalls on CPUs/tasks` crashes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update mainline and linux-next revisions to the latest tags
and fix configs that broke.
NF_FLOW_TABLE_IPV4/6 were removed in:
commit c42ba4290b2147aa033d17f22151494515655d77
netfilter: flowtable: remove ipv4/ipv6 modules
CONFIG_DAX_DRIVER was removed in:
commit afd586f0d06ce3d81b7c474499630fec88833828
dax: remove CONFIG_DAX_DRIVER
BLK_DEV_CRYPTOLOOP was removed in:
commit 47e9624616c80c9879feda536c48c6a3a0ed9835
block: remove support for cryptoloop and the xor transfer
NFT_COUNTER was removed in:
commit 023223dfbfb34fcc9b7dd41e21fbf9a5d5237989
netfilter: nf_tables: make counter support built-in
ICST was renamed to CLK_ICST in:
commit 323fd5955f844d1b6acf1a1af488da460f657ff2
clk: versatile: Rename ICST to CLK_ICST
APPARMOR_INTROSPECT_POLICY was added as requirement for other configs
we enabled in:
commit abfb9c0725f274c75ca2a51684c2dd842a8dc254
apparmor: make export of raw binary profile to userspace optional
|
| |
|
|
|
|
| |
Update to latest upstream, linux-next and kmsan.
KMSAN stopped supporting few configs which depend on crypto
and heap auto-init.
|
| |
|
|
|
|
| |
Update the tags for upstream and -next and update all configs.
This pulls in the CONFIG_WERROR disabled-by-default change.
|
| |
|
|
| |
Update the tags for upstream and -next and update all configs.
|
| | |
|
| | |
|
| |
|
|
| |
Bump kernel revisions to the latest upstream/linux-next/kmsan.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update configs to be based on next-20201124.
With that update, we can enable KFENCE to test KFENCE itself. Note, when
enabled on the KASAN config, we do not expect KFENCE reports to surface,
since KASAN's instrumentation will check an access before the actual
access (which may fault and be handled by KFENCE). Enabling KFENCE is
purely for the benefit of testing KFENCE.
Other notable changes coming to v5.11:
- WIRELESS_WDS subsystem removed
- DLCI subsystem removed
- X25_ASY subsystem removed
- NULL_TTY subsystem removed
|
| | |
|
| |
|
|
|
|
|
|
| |
The original kernel versions were chosen to minimize diffs
with the old configs. Bump kernel versions to the currently
latest releases/tags.
Update #2171
|
|
|
Add config fragments for the new config generation system.
Update #2171
|