mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2025-03-11 22:13:10 +03:00
![]() When two datasets share the same master encryption key, it is safe to clone encrypted blocks. Currently only snapshots and clones of a dataset share with it the same encryption key. Added a test for: - Clone from encrypted sibling to encrypted sibling with non encrypted parent - Clone from encrypted parent to inherited encrypted child - Clone from child to sibling with encrypted parent - Clone from snapshot to the original datasets - Clone from foreign snapshot to a foreign dataset - Cloning from non-encrypted to encrypted datasets - Cloning from encrypted to non-encrypted datasets Reviewed-by: Alexander Motin <mav@FreeBSD.org> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Original-patch-by: Pawel Jakub Dawidek <pawel@dawidek.net> Signed-off-by: Kay Pedersen <mail@mkwg.de> Closes #15544 |
||
---|---|---|
.. | ||
block_cloning_copyfilerange_cross_dataset.ksh | ||
block_cloning_copyfilerange_fallback_same_txg.ksh | ||
block_cloning_copyfilerange_fallback.ksh | ||
block_cloning_copyfilerange_partial.ksh | ||
block_cloning_copyfilerange.ksh | ||
block_cloning_cross_enc_dataset.ksh | ||
block_cloning_disabled_copyfilerange.ksh | ||
block_cloning_disabled_ficlone.ksh | ||
block_cloning_disabled_ficlonerange.ksh | ||
block_cloning_ficlone.ksh | ||
block_cloning_ficlonerange_partial.ksh | ||
block_cloning_ficlonerange.ksh | ||
block_cloning.kshlib | ||
cleanup.ksh | ||
setup.ksh |