Overlapping preopens
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- operating-systems
Research direction
Start from the VFS support and the uvwasi_preopen_t handling shown in the issue, then trace how overlapping mapped paths are resolved and why ordering changes access. No files or tests are named; done requires an agreed behavior for overlapping preopens and coverage for the root and /_wasmer cases.
Written by the indexing model from the issue text.
Description
While working on VFS support, I run into this problem.
A temporary directory is created and I'd like to mount it to the root fs:
uvwasi_preopen_t preopens[3];
preopens[0].mapped_path = "/";
preopens[0].real_path = ".";
preopens[1].mapped_path = ".";
preopens[1].real_path = ".";
preopens[2].mapped_path = "/_wasmer";
preopens[2].real_path = "/tmp/wasm3_temp/1234/_wasmer";
This conflicts with the first (root) entry, and I cannot access _wasmer.
If I reorder preopens, I can access _wasmer, but not the root content.
How should this be handled?
- Dominant language
- C
- Stars
- 272
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 nodejs/uvwasi
-
path_filestat_get returns inval for empty pathsPossibly taken @dannyward630 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
AFLplusplus/AFLplusplus#2903 ·
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
colbymchenry/codegraph#2634 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 8 days