Skip to content

Enable crypto kernel configs in kernel version 6.12#16141

Open
chalamalasetty wants to merge 2 commits into3.0-devfrom
schalam/arm64cryptoconfigs
Open

Enable crypto kernel configs in kernel version 6.12#16141
chalamalasetty wants to merge 2 commits into3.0-devfrom
schalam/arm64cryptoconfigs

Conversation

@chalamalasetty
Copy link
Contributor

@chalamalasetty chalamalasetty commented Mar 7, 2026

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

Enable crypto kernel configs in kernel version 6.12

Change Log
  • Change
    Enable crypto kernel configs in kernel version 6.12
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Pipeline build id: Local validation

%changelog
* Fri Mar 06 2026 Suresh Babu Chalamalasetty <schalam@microsoft.com> - 6.12.57.1-6
- Enable FIPS crypto configs CONFIG_CRYPTO_DH_RFC7919_GROUPS, CONFIG_CRYPTO_ECDSA,
- CONFIG_CRYPTO_ARC4, CONFIG_CRYPTO_DEV_BCM_SPU and their dependencies
Copy link
Member

Choose a reason for hiding this comment

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

mention these changes are only for arm64?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated.

Copy link
Collaborator

@christopherco christopherco left a comment

Choose a reason for hiding this comment

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

One comment to better understand why BCM is being added into the configs.
Rest generally looks okay, though we need a change into the kernel config CI checker to ensure future kernel-hwe version upgrades keep these config changes. Please work with @rlmenge on getting this config checker in place.

# CONFIG_ARCH_ALPINE is not set
# CONFIG_ARCH_APPLE is not set
# CONFIG_ARCH_BCM is not set
CONFIG_ARCH_BCM=y
Copy link
Collaborator

Choose a reason for hiding this comment

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

question(blocking): why are all these Broadcom configs being enabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

BCM related configs are enabled as dependencies for CONFIG_CRYPTO_DEV_BCM_SPU.

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

Labels

3.0-dev PRs Destined for AzureLinux 3.0 Packaging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants