implement RESOLVE_ALLOW_XDEV_SAME
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 44/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- linux, rust
- Domain
- operating-systems, security
Research direction
Read issue #385 and trace how mount crossing errors are handled, then find the path resolution implementations for the existing resolve flags and openat2. Determine how the project represents and compares filesystem IDs (fsid) for a mountpoint and its overmount root. The issue is done when RESOLVE_ALLOW_XDEV_SAME permits crossings only when those IDs match and the behavior is supported for openat2.
Written by the indexing model from the issue text.
Description
In #385 we just skip errors related to /proc/sys but for those kinds of mounts it should be fine to permit mountpoint crossings if the mountpoint and the overmount root are the same filesystem (fsid) as that means that the overlay is the exact same contents just a different set of vfs flags -- which are safe.
Of course, this implies we will need it for openat2 as well.
- 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/cffi bindings/go bindings/python ideas welcome
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
linux/upstream
Difficulty 5/5 Over a week Newbie friendliness 35/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 72/100
cmlarsen/writemorebetter#158 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
scanaislop/aislop#482 ·
Maintainers usually reply within 1 day
-
docs(skills): issue-first should reference an existing Linear ticket instead of filing a duplicateOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day