Chunwei Chen c7a4255f12 Fix zil replay panic when TX_REMOVE followed by TX_CREATE ... If TX_REMOVE is followed by TX_CREATE on the same object id, we need to make sure the object removal is completely finished before creation. The current implementation relies on dnode_hold_impl with DNODE_MUST_BE_ALLOCATED returning ENOENT. While this check seems to work fine before, in current version it does not guarantee the object removal is completed. We fix this by checking if DNODE_MUST_BE_FREE returns successful instead. Also add test and remove dead code in dnode_hold_impl. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: Chunwei Chen <david.chen@nutanix.com> Closes #7151 Closes #8910 Closes #9123 Closes #9145		2019-09-25 11:27:51 -07:00
..
linux.run	Fix zil replay panic when TX_REMOVE followed by TX_CREATE	2019-09-25 11:27:51 -07:00
longevity.run	OpenZFS 9166 - zfs storage pool checkpoint	2018-06-26 10:07:42 -07:00
Makefile.am	Fix out-of-tree build failures	2019-09-25 11:27:48 -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