ROMFS CHECKSUMS
- Dominant language
- C
- Stars
- 4k
- Forks
- 1.7k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 237
Description
```
Description: The ROMFS file system does not verify checksums on either
volume header on on the individual files.
Status: Open
Priority: Low. I have mixed feelings about if NuttX should pay a
performance penalty for better data integrity.
```
Contributor guide
Research direction
The issue identifies ROMFS volume headers and individual files but names no implementation files or tests. Start by locating the ROMFS implementation and existing checksum support; determine the intended verification scope and performance expectations. Done means checksum verification is implemented for the agreed ROMFS data and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100