Open markjdb opened 2 weeks ago
This apparent bug was introduced in commit 0409d3327371 ("Improve zpool status output, list all affected datasets")
, perhaps @gamanakis could take a look?
Thanks for catching this, you are correct, I will submit a PR.
@markjdb could you take a look at #16273? Once it runs through the ZTS I will mark it as non-draft.
@markjdb could you take a look at #16273? Once it runs through the ZTS I will mark it as non-draft.
It looks fine to me. I applied the patch locally and kicked off another test run with KASAN.
@markjdb could you take a look at #16273? Once it runs through the ZTS I will mark it as non-draft.
It looks fine to me. I applied the patch locally and kicked off another test run with KASAN.
I didn't see any problems with the patch.
System information
zfs-2.2.99-517-FreeBSD_ge2357561b zfs-kmod-2.2.99-517-FreeBSD_ge2357561b
Describe the problem you're observing
Running the ZFS test suite with KASAN triggered a panic:
This corresponds to the dereference of
origin_head
at the very end ofdsl_dataset_promote_sync()
.Describe how to reproduce the problem
It is not consistently reproducible, so far I only hit this once.
I believe the problem is that
origin_head
andhds
are not safe to dereference afterpromote_rele()
is called. Either the object IDs should be loaded before the references are released, or references should be released after callingspa_swap_errlog()
.