zfs_blkptr_verify should continue after zfs_panic_recover
This is reported by FreeBSD Coverity Scan, CID 1258589 should be referenced.
In ZFS many places we use zfs_panic_recover, where the code is able to continue after hitting the asserted condition, if system administrator requests so.
The new zfs_blkptr_verify should take this into account and do not do e.g. access vd->vdev_ops after checking if vd is NULL.
Updated by Electric Monk over 4 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit 5897eb49ccde82d19214b71984f57935e7e313d1 Author: Justin Gibbs <email@example.com> Date: 2015-05-27T14:09:18.000Z 5438 zfs_blkptr_verify should continue after zfs_panic_recover Reviewed by: Matthew Ahrens <firstname.lastname@example.org> Reviewed by: George Wilson <email@example.com> Reviewed by: Xin LI <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>