Open Bug 1870868 Opened 7 months ago Updated 4 months ago

Map `ERROR_FILE_CORRUPT` to `NS_ERROR_FILE_CORRUPTED` not `NS_ERROR_FILE_FS_CORRUPTED`

Categories

(Core :: Storage: Quota Manager, defect, P3)

defect

Tracking

()

People

(Reporter: mvanstraten, Assigned: mvanstraten)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Currently, we map the Windows ERROR_FILE_CORRUPT to NS_ERROR_FILE_FS_CORRUPTED, which is later used in checks, such as when iterating over directory entries. We aim to differentiate between NS_ERROR_FILE_FS_CORRUPTED and NS_ERROR_FILE_CORRUPTED in these cases.

Currently, Windows ERROR_FILE_CORRUPT is mapped to NS_ERROR_FILE_FS_CORRUPTED in our codebase. This mapping is utilized in various checks, including directory entry iteration. This commit refactors the error mapping to distinguish between NS_ERROR_FILE_FS_CORRUPTED and NS_ERROR_FILE_CORRUPTED specifically for cases such as iterating over directory entries. This change is aimed at providing more precise handling of file system corruption issues, improving the accuracy of error reactions during directory operations.

Blocks: 1886743
You need to log in before you can comment on or make changes to this bug.