Skip to content

fix(kernel): restore required configs and disable unused features - #19862

Draft
Rachel Menge (rlmenge) wants to merge 4 commits into
microsoft:4.0from
rlmenge:rlmenge/4.0/config-json
Draft

Rachel Menge (rlmenge) wants to merge 4 commits into
microsoft:4.0from
rlmenge:rlmenge/4.0/config-json

Conversation

@rlmenge

Copy link
Copy Markdown
Contributor

Summary
Update the Azure Linux 6.18 kernel configs and remove stale config-checker overrides so the existing policy applies.

Changes

  • IO latency protection: enable CONFIG_BLK_CGROUP_IOLATENCY=y on x86_64 and arm64.
  • AMD compute support: enable CONFIG_HSA_AMD, CONFIG_HSA_AMD_SVM, and CONFIG_HSA_AMD_P2P on x86_64. Keep CONFIG_DRM_AMDGPU=m.
  • DMI compatibility: restore CONFIG_DMI_SYSFS=m on x86_64 for raw DMI table access. CONFIG_DMIID remains unchanged.
  • Feature disablements: disable Smack, ROSE, and kernel SMB serving through ksmbd on both architectures, including dependent settings.
  • Deprecated XFS format: disable CONFIG_XFS_SUPPORT_V4 on both architectures.
  • Refresh the kernel lock and regenerate rendered configs.

Copilot AI balanced review requested due to automatic review settings November 1, 2026 00:55

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 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

@rlmenge

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.

@rlmenge
Rachel Menge (rlmenge) marked this pull request as ready for review November 1, 2026 18:15
@rlmenge
Rachel Menge (rlmenge) requested a review from a team as a code owner November 1, 2026 18:15
@rlmenge
Rachel Menge (rlmenge) marked this pull request as draft November 1, 2026 21:56
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>
Copilot AI balanced review requested due to automatic review settings November 1, 2026 22:16

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 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

@rlmenge

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants