Repository navigation
Conversation
MSan runners were failing in the weekly CT tests, and Claude was able to diagnose the issue: in runners with vm.mmap_rnd_bits=32, MSan needs to sometimes re-exec itself with `personality(ADDR_NO_RANDOMIZE)`, which Docker's default seccomp profile blocks. The fix is to disable seccomp for the MSan container, so that this re-exec can succeed without being blocked. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Owen Waldron <owen.waldron@uwaterloo.ca>
Contributor
Author
|
@pablo-gf please take a look if you can, since I don't know enough about the |
owaldron
marked this pull request as ready for review
November 18, 2026 21:23
owaldron
requested review from
baentsch,
dstebila and
xuganyu96
as code owners
November 18, 2026 21:23
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
MSan jobs were failing over the last couple weekly CT tests (2026-11-14, 2026-11-07), and Claude was able to diagnose the issue: in runners with
vm.mmap_rnd_bits=32, MSan needs to sometimes re-exec itself withpersonality(ADDR_NO_RANDOMIZE), which Docker's default seccomp profile blocks.The fix is to disable seccomp for the memsan runner's containers, so that this re-exec can succeed without being blocked. A run of the
ct-testson my fork succeeds after this flag is added: https://github.com/owaldron/liboqs/actions/runs/44388550257Along with #2714, this should get weekly CI green again.
Generative AI Disclosure: Claude Code (Claude Opus 5.5) was used to help diagnose the issue, discuss fixes, and aid with understanding.