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
..
linux.run	ZVOLs should not be allowed to have children	2019-02-08 15:44:15 -08:00
longevity.run	OpenZFS 9166 - zfs storage pool checkpoint	2018-06-26 10:07:42 -07:00
Makefile.am	Fix "file is executable, but no shebang" warnings	2018-04-06 16:34:21 -07:00
perf-regression.run	OpenZFS 9184 - Add ZFS performance test for fixed blocksize random read/write IO	2018-07-02 13:46:06 -07:00