Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

openat2 support for RESOLVE_NO_DOTDOT

Open
  • Is something wrong?
#366 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux, rust
Domain
backend, security

Research direction

Start by reading the path resolution implementation and existing tests for openat2 semantics; the issue does not name specific files or tests. Determine how RESOLVE_NO_DOTDOT should behave for the userspace procfs resolver and what matching openat2 semantics require, then add coverage showing the resolver rejects paths containing parent-directory components.

Written by the indexing model from the issue text.

Description

linux/upstream

We have to do this for our userspace procfs resolver, it would be quite nice to have the semantics match with openat2.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cyphar/libpathrs

All issues in cyphar/libpathrs

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.