seccomp: goToNative values for loong64 and mipsle have no matching nativeToSeccomp key
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
Research direction
Start at setupSeccomp and inspect the goToNative and nativeToSeccomp mappings, including the SCMP_ARCH_LOONGARCH64 entry in default.json. Align the two keys and add a test that every goToNative value has a nativeToSeccomp entry; done means Architectures is populated for loong64 and mipsle.
Written by the indexing model from the issue text.
Description
setupSeccomp does arch = goToNative[runtime.GOARCH] and then looks arch up in nativeToSeccomp. Two entries don't line up:
- goToNative["loong64"] = "loongarch64", but nativeToSeccomp has "loong64".
- goToNative["mipsle"] = "mipsel", but nativeToSeccomp has "mipsle".
On those two GOARCH values the archMap block is skipped and Architectures is not populated. For loong64, default.json has a SCMP_ARCH_LOONGARCH64 entry that never gets used. I haven't run this on loong64 hardware, so the runtime impact is inferred from reading the code.
Suggested fix: rename the two nativeToSeccomp keys to loongarch64 and mipsel, and add a test that every goToNative value has a nativeToSeccomp entry.
- Dominant language
- Go
- Stars
- 13
- Forks
- 17
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from moby/profiles
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
moby/profiles#24 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Add SolentaPossibly taken @sharmao07 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
slavakurilyak/awesome-ai-agents#760 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
agent-review-finding bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jordansmall/spindrift#5281 ·
Maintainers usually reply within 1 day