loli10K d8d418ff0c ZVOLs should not be allowed to have children ... zfs create, receive and rename can bypass this hierarchy rule. Update both userland and kernel module to prevent this issue and use pyzfs unit tests to exercise the ioctls directly. Note: this commit slightly changes zfs_ioc_create() ABI. This allow to differentiate a generic error (EINVAL) from the specific case where we tried to create a dataset below a ZVOL (ZFS_ERR_WRONG_PARENT). Reviewed-by: Paul Dagnelie <pcd@delphix.com> Reviewed-by: Matt Ahrens <mahrens@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com>		2019-02-08 15:44:15 -08:00
..
bindings	pyzfs: python3 support (library 1/2)	2019-01-06 10:39:41 -08:00
test	ZVOLs should not be allowed to have children	2019-02-08 15:44:15 -08:00
__init__.py	pyzfs: python3 support (library 1/2)	2019-01-06 10:39:41 -08:00
_constants.py	ZVOLs should not be allowed to have children	2019-02-08 15:44:15 -08:00
_error_translation.py	ZVOLs should not be allowed to have children	2019-02-08 15:44:15 -08:00
_libzfs_core.py	ZVOLs should not be allowed to have children	2019-02-08 15:44:15 -08:00
_nvlist.py	pyzfs: python3 support (library 2/2)	2019-01-06 10:39:41 -08:00
ctypes.py	pyzfs: python3 support (library 2/2)	2019-01-06 10:39:41 -08:00
exceptions.py	ZVOLs should not be allowed to have children	2019-02-08 15:44:15 -08:00