Support locking file
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
Do you think this is better provided as a primitive by
litebox::fs::FileSystemor do you think it is better managed as a lock within the Linux shim? I am leaning towards possibly adding afn lock_fd(fd: &Fd) -> ...(and unlock) to theFileSystemtrait, so that you can take a lock at the start of readv and thus get atomicity. Please open an issue to track this if so.
Originally posted by @jaybosamiya-ms in https://github.com/MSRSSP/litebox/pull/67#discussion_r2021904174
Contributor 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.
Research direction
Start by reviewing the FileSystem trait, the Linux shim, and the readv path mentioned in the issue. Determine the locking and unlocking API needed for file descriptors and whether it provides atomicity across readv; done means the design and affected entry points are clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100