apply patch to fix jitterentropy init in kernel and kernel-64k #12239
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./LICENSES-AND-NOTICES/SPECS/data/licenses.json
,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md
,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
We are seeing frequent, though not 100% repro, kernel panics on boot on certain vm sizes of arm64 FIPS machines in azure:
This indicates a failure to generate enough entropy in the kernel's crypto module.
There have been multiple changes to this code upstream that address the core issue and allow configuration of certain jitter entropy parameters. For this change, I've taken four upstream commits:
Change Log
Does this affect the toolchain?
YES
Associated issues
Test Methodology
-- Created a an azure vm that regularly reproed the issue. Upgraded with kernel from the buddy build and rebooted 30+ times -- no reproes.