| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
New debugging configs in net-next.
Eric asks to enable them.
|
| |
|
|
|
|
| |
All of lockdep comes with a number of config options, so let's refactor
it into a separate lockdep.yml, which makes it easier to disable
selectively.
|
| | |
|
| |
|
|
|
|
|
|
| |
Once we've bumped other capacity values,
"BUG: MAX_STACK_TRACE_ENTRIES too low!" started happening as well:
https://syzkaller.appspot.com/bug?id=4ebb151b4e3ef885165669fea5b4cf1f2e353ab0
https://groups.google.com/g/syzkaller-upstream-moderation/c/8FK5kogGHM4
Bump LOCKDEP_STACK_TRACE_BITS by 1.
|
| |
|
|
|
|
|
| |
Add constraints for configs not present in v4.15.
I tentatively marked all of them as v4.16.
If we support something in between v4.15 and v5.4
in future we may need to refine them.
|
| |
|
|
|
|
|
|
|
|
| |
We are seeing the following warnings from LOCKDEP:
BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
BUG: MAX_LOCKDEP_CHAINS too low!
BUG: MAX_LOCKDEP_ENTRIES too low!
Increase the corresponding capacity constants.
|
| | |
|
| |
|
|
|
| |
DEBUG_TIMEKEEPING enables some debug checks.
FW_LOADER_USER_HELPER was enabled on arm/android but not on x86_64.
|
| |
|
|
| |
Enable some new configs that look reachable in VMs.
|
| |
|
|
| |
These instances ignore WARNINGs, so they don't want panic_on_warn.
|
| | |
|
| |
|
|
| |
It seems to be working now.
|
| |
|
|
| |
Also bump KMSAN to latest kmsan-v5.10-rc4.
|
| |
|
|
|
|
| |
Qemu emulation makes execution slower so we need to scale all
hang/stall timeouts as well. Scale them by 3 to account for
sys/targets.Timeouts.Scale which is set to 3.
|
| |
|
|
| |
Enable new things in v5.11 that we can reach.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
HW_RANDOM_VIRTIO/RANDOM_TRUST_CPU/RANDOM_TRUST_BOOTLOADER
help to initialize random pool faster.
+mark some x86_64-specific configs as such
in preparataion for arm64 support.
|
| |
|
|
|
|
|
| |
Resolve all TODOs that were left during the switch
from old to new configs to minimize diffs.
Update #2171
|
|
|
Add config fragments for the new config generation system.
Update #2171
|