Richard Yao 72c99dc959 Handle possible null pointers from malloc/strdup/strndup() ... GCC 12.1.1_p20220625's static analyzer caught these. Of the two in the btree test, one had previously been caught by Coverity and Smatch, but GCC flagged it as a false positive. Upon examining how other test cases handle this, the solution was changed from `ASSERT3P(node, !=, NULL);` to using `perror()` to be consistent with the fixes to the other fixes done to the ZTS code. That approach was also used in ZED since I did not see a better way of handling this there. Also, upon inspection, additional unchecked pointers from malloc()/calloc()/strdup() were found in ZED, so those were handled too. In other parts of the code, the existing methods to avoid issues from memory allocators returning NULL were used, such as using `umem_alloc(size, UMEM_NOFAIL)` or returning `ENOMEM`. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tony Hutter <hutter2@llnl.gov> Signed-off-by: Richard Yao <richard.yao@alumni.stonybrook.edu> Closes #13979		2022-10-06 17:18:40 -07:00
..
callbacks	autoconf: use include directives instead of recursing down tests (mostly)	2022-05-10 10:20:09 -07:00
cmd	Handle possible null pointers from malloc/strdup/strndup()	2022-10-06 17:18:40 -07:00
include	zed: mark disks as REMOVED when they are removed	2022-09-28 09:48:46 -07:00
tests	zed: mark disks as REMOVED when they are removed	2022-09-28 09:48:46 -07: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