[FEATURE] mechanism to ensure the consistent locking order
- Dominant language
- C
- Stars
- 4k
- Forks
- 1.7k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 237
Description
### Is your feature request related to a problem? Please describe.
it would be nice to have some debug feature which can detect issues like https://github.com/apache/nuttx/issues/15314
### Describe the solution you'd like
precedents:
https://man.freebsd.org/cgi/man.cgi?witness(4)
https://docs.kernel.org/locking/lockdep-design.html
### Describe alternatives you've considered
although adhoc local assertions like https://github.com/yamt/incubator-nuttx/commit/ac3dda4f4f85d5774a5e05ec0595fe572110c947
can work, it would be nicer to have a generic mechanism in the upstream.
### Verification
- [X] I have verified before submitting the report.
Contributor guide
Research direction
Read issue #15314 and the referenced FreeBSD witness(4) and Linux lockdep-design precedents first. Review merged pull request #18886 to understand the existing work; done would be a defined, generic upstream debug mechanism for detecting inconsistent lock ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100