[Work Item #19887] Resolved ptests failure in util-linux package

[SumitJenaHCL]

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

What does the PR accomplish, why was it needed?
The package has regressed ptests under util-linux. The lslocks ofd--w ptest was flaky because proc exposed lock holders from unrelated host processes, intermittently breaking the row-count assertion. Running %check inside unshare --pid --fork --mount-proc gives the test a fresh PID namespace, so lslocks only sees the test's own processes — making the result deterministic.

Change Log

• SPECS/util-linux/util-linux.spec
• toolkit/resources/manifests/package/pkggen_core_aarch64.txt
• toolkit/resources/manifests/package/pkggen_core_x86_64.txt
• toolkit/resources/manifests/package/toolchain_aarch64.txt
• toolkit/resources/manifests/package/toolchain_x86_64.txt

Does this affect the toolchain?

YES

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1118450&view=results