| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
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
|