staging/stintel/config, branch master

kernel: make KERNEL_DEBUG_INFO=n disable debug information

2026-10-21T16:49:00Z

Since Linux 5.18, CONFIG_DEBUG_INFO has no prompt. It is selected by the "Debug information" choice, which the generic config sets to DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT. Writing "# CONFIG_DEBUG_INFO is not set" is therefore ignored, and the kernel is built with debug information even when KERNEL_DEBUG_INFO is disabled, which is the default on SMALL_FLASH targets. Add a hidden KERNEL_DEBUG_INFO_NONE option that selects DEBUG_INFO_NONE in the choice when KERNEL_DEBUG_INFO is disabled. Firmware images are not affected, as the kernel and modules are stripped, but build time and disk usage are. Signed-off-by: Sander van Deijck Link: https://github.com/openwrt/openwrt/pull/26065 Signed-off-by: Christian Marangi

kernel: drop dead filesystem ACL options

2026-10-21T16:47:53Z

None of these options has any effect on the kernel configuration: - CIFS_ACL: removed upstream, ACL support is always built in - HFS_FS_POSIX_ACL, HFSPLUS_FS_POSIX_ACL: not kernel symbols (hfsplus dropped its ACL support) - NFS_V3_ACL_SUPPORT, NFSD_V2_ACL_SUPPORT, NFSD_V3_ACL_SUPPORT: wrong names, the kernel symbols are NFS_V3_ACL, NFSD_V2_ACL and NFSD_V3_ACL - NFS_ACL_SUPPORT: has no prompt in the kernel and is only set when selected by the options above, so setting it directly is ignored The NFS options are removed rather than renamed: enabling the real symbols builds nfs_acl.ko, which is not packaged, and nfsv3.ko would fail to load without it. KERNEL_FS_POSIX_ACL still defaults to y with USE_FS_ACL_ATTR, so the generated kernel configuration does not change. Signed-off-by: Sander van Deijck Link: https://github.com/openwrt/openwrt/pull/26064 Signed-off-by: Christian Marangi

kernel: drop removed cgroup and block IO options

2026-10-21T16:47:52Z

These kernel symbols no longer exist, so the options are silently ignored when the kernel is configured: - MEMCG_KMEM: kernel memory accounting is always part of MEMCG - CFQ_GROUP_IOSCHED: removed together with the CFQ scheduler (5.0) - BLK_DEV_THROTTLING_LOW: the .low limit interface was removed - DEBUG_BLK_CGROUP: removed Update the KERNEL_BLK_CGROUP help text to refer to BFQ_GROUP_IOSCHED, as the kernel help text does. Signed-off-by: Sander van Deijck Link: https://github.com/openwrt/openwrt/pull/26064 Signed-off-by: Christian Marangi

kernel: drop KERNEL_UBSAN_SANITIZE_ALL

2026-10-21T16:47:52Z

CONFIG_UBSAN_SANITIZE_ALL was removed upstream in Linux 6.9. When UBSAN is enabled, the whole kernel is now instrumented by default, so the option has no effect anymore. Signed-off-by: Sander van Deijck Link: https://github.com/openwrt/openwrt/pull/26064 Signed-off-by: Christian Marangi

kernel: remove kmods for drivers dropped upstream

2026-10-20T08:19:03Z

ReiserFS was removed from the kernel in 6.13 and the STM32 CRC32 driver is no longer part of kernel 6.18, so kmod-fs-reiserfs and kmod-stm32-crc32 can no longer be built. Remove both packages and drop kmod-fs-reiserfs from the gemini NAS default packages. Also remove the KERNEL_REISER_FS_POSIX_ACL option, which never mapped to an existing kernel symbol (CONFIG_REISERFS_FS_POSIX_ACL), and the stale CONFIG_REISERFS_* symbols from the generic 6.18 kernel config. Signed-off-by: Sander van Deijck Link: https://github.com/openwrt/openwrt/pull/25965 Signed-off-by: Robert Marko

build: drop implicit gzip of ext4 images

2026-10-06T09:32:34Z

With CONFIG_TARGET_IMAGES_GZIP enabled, which is the default, ext4 images are gzipped when they are copied to $(BIN_DIR), unless their name ends with .gz or .dtb. This causes several problems: - The JSON info contains the uncompressed name and hash, so profiles.json lists images which don't exist on the download server: profiles.json: openwrt-at91-sam9x-atmel_at91sam9263ek-ext4-root.ubi sha256sums: openwrt-at91-sam9x-atmel_at91sam9263ek-ext4-root.ubi.gz - The image is gzipped as a whole, including the metadata and signature added by append-metadata. fwtool looks for them at the end of the file, so sysupgrade rejects these images. Explicitly gzipped images run append-metadata after gzip instead. - A rule for the gzipped name is defined for every image, which clashes with images that are built both plain and gzipped, as it was the case for malta. The previous commits removed the ext4 images which can't be used and gzip the remaining ones explicitly, so drop the implicit gzip. The file name in $(BIN_DIR) is now always the one from IMAGES. Targets wanting gzipped images define them explicitly, e.g. sdcard.img.gz, or select them via CONFIG_TARGET_IMAGES_GZIP like x86, armsr, loongarch64 and malta. Limit the option to these targets. The ext4 kernel.bin and factory.bin of ixp4xx, which only contain the kernel, and the optional ext4 VM images of x86 and armsr are now stored uncompressed, like their squashfs counterparts. Link: https://github.com/openwrt/openwrt/pull/25658 Signed-off-by: Paul Spooren

build: remove the AUDIO_SUPPORT and DISPLAY_SUPPORT symbols

2026-09-29T14:29:43Z

Nothing tests either symbol any more. AUDIO_SUPPORT was also selected by PCI_SUPPORT and USB_SUPPORT, which stood for "a sound card could be plugged in here": audio hardware sits behind MMC, SPI, a Bluetooth UART or an SoC PCM block just as often, so the inference never held. The display feature was derived from a literal CONFIG_VGA_CONSOLE or CONFIG_FB in a kernel fragment, which misses every target whose fbdev came from DRM emulation. Delete both symbols, the two selects, the feature translations and the derivation. Signed-off-by: Daniel Golle

build: gate the VM image formats on their target features

2026-09-24T21:33:28Z

The x86 and armsr targets declare the vdi, vmdk and vhdx features, but VDI_IMAGES, VMDK_IMAGES and VHDX_IMAGES depend on a hardcoded target list instead, so the features select nothing and a target opting in has to edit config/Config-images.in. Give them USES_VDI, USES_VMDK and USES_VHDX in the same shape as the other image formats and depend on those. The set of targets offering each format is unchanged. Signed-off-by: Daniel Golle

kernel: add KERNEL_TIME_NS Kconfig knob

2026-09-18T15:03:13Z

Enable time namespaces by default, following the existing pattern of enabling all container-relevant features by default with optional opt-out. The knob carries no architecture dependency of its own. TIME_NS is gated on GENERIC_VDSO_TIME_NS on 6.12 and on GENERIC_GETTIMEOFDAY on 6.18, so the set of architectures able to honour it differs per kernel version. Where the dependency is unmet the kernel drops the symbol during syncconfig, as it does for the other options offered unconditionally here. Signed-off-by: Daniel Golle

build: gate firmware image signing behind SIGN_FIRMWARE

2026-07-20T08:33:41Z

Firmware image signing in append-metadata/append-gl-metadata was conditional only by the presence of the build key. Add an explicit SIGN_FIRMWARE option (default enabled except with BUILDBOT) so appending the fwtool signature can be toggled on its own. It's disable on buildbot since we use a decentralized building with no individual keys on builders. Instead, a fake key is currently used, which adds an insecure signature. The future of signing firmware and key distribution across the build infrastructure should be discussed separately. Link: https://github.com/openwrt/openwrt/pull/24291 Signed-off-by: Paul Spooren