Recognize irregular ioctls and abort if they're unhandled
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
We're having several problems in #876 with code making irregular ioctls (that don't use the _IOC() macro) and rr not recognizing that they have outparams that need to be recorded. We should instead abort.
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 issue #876 and the rr handling for ioctls that do not use the _IOC() macro. Determine where an irregular ioctl with an unrecognized out parameter is currently accepted; done means rr aborts instead of continuing when such an ioctl is unhandled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100