Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport #14119 to zfs-2.1.7-staging #14139

Merged

Commits on Nov 3, 2022

  1. Deny receiving into encrypted datasets if the keys are not loaded

    Commit 68ddc06 introduced support
    for receiving unencrypted datasets as children of encrypted ones but
    unfortunately got the logic upside down. This resulted in failing to
    deny receives of incremental sends into encrypted datasets without
    their keys loaded. If receiving a filesystem, the receive was done
    into a newly created unencrypted child dataset of the target. In
    case of volumes the receive made the target volume undeletable since
    a dataset was created below it, which we obviously can't handle.
    Incremental streams with embedded blocks are affected as well.
    
    We fix the broken logic to properly deny receives in such cases.
    
    Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
    Signed-off-by: Attila Fülöp <attila@fueloep.org>
    Closes openzfs#13598
    Closes openzfs#14055
    Closes openzfs#14119
    AttilaFueloep committed Nov 3, 2022
    Configuration menu
    Copy the full SHA
    9086149 View commit details
    Browse the repository at this point in the history