Repository navigation
fix(kernel): restore required configs and disable unused features - #19862
Rachel Menge (rlmenge) wants to merge 4 commits into
Conversation
There was a problem hiding this comment.
🔵 Needs a closer look
The kernel configuration changes retain the existing RPM version/release, preventing normal upgrades from delivering them to systems with that kernel installed; the release must be incremented, the changelog updated, and the lock and rendered outputs refreshed.
No open issues 🎉
What changed in this PR
This PR aligns the Azure Linux 6.18 kernel configurations with existing policy, restoring required capabilities and disabling unused features.
Changes:
- Enables I/O latency protection on both architectures and restores AMD compute support and raw DMI access on x86_64.
- Disables Smack, ROSE, ksmbd, and deprecated XFS v4 support on both architectures.
- Removes stale config-checker overrides and updates the kernel lock and rendered configs.
| File | Description |
|---|---|
specs/k/kernel/6.18-x86_64-azl.config |
Mirrors the x86_64 configuration changes in rendered output. |
specs/k/kernel/6.18-aarch64-azl.config |
Mirrors the arm64 configuration changes in rendered output. |
scripts/ci/kernel/kernel-config-checker/kernel_config_checker/kernel_configs_json/azl4-os-required-kernel-configs.json |
Removes overrides so existing requirements apply. |
locks/kernel.lock |
Refreshes the component input fingerprint. |
base/comps/kernel/6.18-x86_64-azl.config |
Restores required capabilities and disables unwanted features on x86_64. |
base/comps/kernel/6.18-aarch64-azl.config |
Enables I/O latency protection and disables unwanted features on arm64. |
Review effort: Balanced
|
/azp run |
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. |
Restore the cgroup IO latency controller in the kernel 6.18 configs for x86_64 and arm64. Leaving it disabled removes the interface used to protect latency-sensitive workloads from competing block IO. - Enable CONFIG_BLK_CGROUP_IOLATENCY=y on both architectures. - Remove the stale checker override that disabled the controller. - Refresh the kernel lock and regenerate both rendered configs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Restore AMD HSA/KFD compute support in the x86_64 kernel 6.18 config. The disabled configuration prevents the AMDGPU driver from providing the HSA compute functionality expected by GPU workloads. - Enable CONFIG_HSA_AMD, CONFIG_HSA_AMD_SVM, and CONFIG_HSA_AMD_P2P. - Keep CONFIG_DRM_AMDGPU=m; the driver remains a loadable module. - Remove stale HSA checker overrides so the existing policy applies. - Refresh the kernel lock and regenerate the rendered x86_64 config. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Restore CONFIG_DMI_SYSFS=m in the x86_64 kernel 6.18 config for compatibility with consumers of raw DMI table access through sysfs. This does not control all DMI identification interfaces: CONFIG_DMIID remains enabled and unchanged. - Remove the stale checker override that disabled DMI sysfs access. - Retain the existing module policy for CONFIG_DMI_SYSFS. - Refresh the kernel lock and regenerate the rendered x86_64 config. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Restore the existing disabled policy for these features in the kernel 6.18 configs on x86_64 and arm64. Smack is not in the configured LSM list, and no requirement was identified for ROSE amateur-radio networking or kernel SMB serving through ksmbd. - Disable CONFIG_SECURITY_SMACK, CONFIG_ROSE, and CONFIG_SMB_SERVER. - Disable CONFIG_XFS_SUPPORT_V4 for the deprecated crc=0 format. - Remove dependent Smack and SMB-server settings. - Remove stale checker overrides so the default disabled policy applies. - Refresh the kernel lock and regenerate both architecture configs. SELinux, SMB client support, and userspace Samba remain unchanged. XFS V5 support remains enabled. Existing XFS V4 (crc=0) volumes cannot be mounted with the resulting kernel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
93775dd to
5c5818e
Compare
There was a problem hiding this comment.
🔵 Needs a closer look
The kernel changes affect GPU, cgroup I/O, and XFS behavior across both architectures, while required build, RPM inspection, and runtime validation remain unavailable and need human verification.
No open issues 🎉
Review effort: Balanced
|
/azp run |
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. |
Summary
Update the Azure Linux 6.18 kernel configs and remove stale config-checker overrides so the existing policy applies.
Changes