oromenahar 121924575e Allow block cloning across encrypted datasets ... 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		2024-01-08 16:11:39 -08:00
..
callbacks	Split functional testings via github action matrix	2023-03-15 10:41:05 -07:00
cmd	FreeBSD: Reduce divergence from in-tree sources	2023-10-10 19:19:09 -07:00
include	ZTS: Fix 'could not unmount datasets' on Alma 9	2023-11-20 13:20:56 -08:00
tests	Allow block cloning across encrypted datasets	2024-01-08 16:11:39 -08:00
.gitignore	autoconf: use include directives instead of recursing down cmd	2022-05-10 10:18:38 -07:00
Makefile.am	autoconf: use include directives instead of recursing down tests (mostly)	2022-05-10 10:20:09 -07:00