Fix dataset cloning and renaming to and from an encryption root #15475
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.
Motivation and Context
We intend to keep all datasets with an identical encryption root inside the child dataset hierarchy of the encryption root.
Currently it is forbidden to move an encrypted dataset ouside its encryption root but this is incomplete. We need to prevent cloning an encrypted dataset outside of its encryption root and renaming or cloning an unencrypted dataset under an encryption root.
Description
How Has This Been Tested?
Tested on FreeBSD
Types of changes
Checklist:
Signed-off-by
.