azurelinux
azurelinux copied to clipboard
Enable CONFIG_NFT_OBJREF
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
- [x] The toolchain has been rebuilt successfully (or no changes were made to it)
- [x] The toolchain/worker package manifests are up-to-date
- [x] Any updated packages successfully build (or no packages were changed)
- [x] Packages depending on static components modified in this PR (Golang,
*-staticsubpackages, etc.) have had theirReleasetag incremented. - [x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
- [x] All package sources are available
- [x] cgmanifest files are up-to-date and sorted (
./cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json) - [x] LICENSE-MAP files are up-to-date (
./SPECS/LICENSES-AND-NOTICES/data/licenses.json,./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md,./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON) - [x] All source files have up-to-date hashes in the
*.signatures.jsonfiles - [x]
sudo make go-tidy-allandsudo make go-test-coveragepass - [x] Documentation has been updated to match any changes to the build system
- [x] Ready to merge
Summary
Enable CONFIG_NFT_OBJREF
Add the nft_objref module to AMD64 for object reference support for nftables. This allows for AMD customers using nftables to get instight into their running Routing Policy (RP) policies.
This config is already enabled in ARM64. Note that option is builtin for kernel 6.6.X and the option itself was removed https://github.com/microsoft/CBL-Mariner-Linux-Kernel/commit/d037abc2414b4539401e0e6aa278bedc4628ad69
Change Log
- Enable CONFIG_NFT_OBJREF
Does this affect the toolchain?
YES
Associated issues
- https://microsoft.visualstudio.com/OS/_workitems/edit/48734550?src=WorkItemMention&src-action=artifact_link
Test Methodology
- Pipeline build id (in progress): https://dev.azure.com/mariner-org/mariner/_build/results?buildId=542144&view=results
Making draft as this may not be the complete config set needed for scenario