openat2 support for RESOLVE_WITH_ROOTFD
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the openat2(2) interface and the existing RESOLVE_IN_ROOT and RESOLVE_BENEATH handling in libpathrs. The issue proposes ways to let rootfd and cwdfd differ, but does not identify files, tests, or a settled API design; determine the intended interface and assess its impact before implementation. Done means supporting the chosen flag semantics and covering them with tests for distinct rootfd and cwdfd values.
Written by the indexing model from the issue text.
Description
The rootfd and cwdfd always having to be the same fd with openat2(2) is quite inconvenient and it makes implementing things like symlink-follow O_CREAT support not really possible in a nice way (i.e., without completely re-doing lookups an unbounded number of times), and some other problems are almost intractable without this interface.
Options are to have one bit (RESOLVE_WITH_ROOTFD) that must be used with RESOLVE_IN_ROOT or RESOLVE_BENEATH, or just have two new versions of those flags (RESOLVE_IN_ROOTFD, RESOLVE_BENEATH_ROOTFD or RESOLVE_BENEATHFD).
- Dominant language
- Rust
- Stars
- 146
- Forks
- 12
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 cyphar/libpathrs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
rust tests
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
api/procfs linux/upstream
Difficulty 4/5 3-5 days Newbie friendliness 44/100
-
api/cffi bindings/go bindings/python ideas welcome
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
linux/upstream
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in cyphar/libpathrs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
storytold/photocraft#5710 ·
Maintainers usually reply within 1 day
-
Two tests fail on a Windows checkout: a CRLF parse in feature_walk_tests, an 8.3 TEMP path in libraries_testsPossibly taken @CamWight claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bherbruck/solvecraft#1186 · 1 comment ·
-
area: screenshot audit bug good first issue priority: P3 security severity: info type: correctness
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pierruno-labs/prowl#31 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
limitlessprojects/Go-Hybrid#50 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day