Replace Incompatible::DirectoryEncrypted
with Ext4Error::Encrypted
#412
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reasons for moving this from
Incompatible
to a top-level error:Incompatible
prevent the filesystem from being loaded. However, the lack of support for encrypted directories just prevents those specific paths from being loaded. So any otherIncompatible
error is essentially fatal, butIncompatible::DirectoryEncrypted
can be handled.The new error is named
Encrypted
instead ofDirectoryEncrypted
because although ext4 encryption is directory based, files within a directory can of course be encrypted too, so a more general name is appropriate.#389