diff options
author | Matthew Ahrens <[email protected]> | 2023-01-09 16:43:45 -0800 |
---|---|---|
committer | GitHub <[email protected]> | 2023-01-09 16:43:45 -0800 |
commit | 40d7e971ffc16b2ef993a6e9da40a8b3ca91ad01 (patch) | |
tree | b981e16598ebcf880516dd20e184577800c7327e /module/zfs/zio.c | |
parent | 44a78c05b3946804e98686dd5f22d57f00186547 (diff) |
ztest fails assertion in zio_write_gang_member_ready()
Encrypted blocks can have up to 2 DVA's, as the third DVA is reserved
for the salt+IV. However, dmu_write_policy() allows non-encrypted
blocks (e.g. DMU_OT_OBJSET) inside encrypted datasets to request and
allocate 3 DVA's, since they don't need a salt+IV (they are merely
authenicated).
However, if such a block becomes a gang block, the gang code incorrectly
limits the gang block header to 2 DVA's. This leads to a "NDVAs
inversion", where a parent block (the gang block header) has less DVA's
than its children (the gang members), causing an assertion failure in
zio_write_gang_member_ready().
This commit addresses the problem by only restricting the gang block
header to 2 DVA's if the block is actually encrypted (and thus its gang
block members can have at most 2 DVA's).
Reviewed-by: Richard Yao <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Matthew Ahrens <[email protected]>
Closes #14250
Closes #14356
Diffstat (limited to 'module/zfs/zio.c')
-rw-r--r-- | module/zfs/zio.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/module/zfs/zio.c b/module/zfs/zio.c index 9ae245866..5d7ed6d58 100644 --- a/module/zfs/zio.c +++ b/module/zfs/zio.c @@ -2826,7 +2826,7 @@ zio_write_gang_block(zio_t *pio, metaslab_class_t *mc) * have a third copy. */ gbh_copies = MIN(copies + 1, spa_max_replication(spa)); - if (gio->io_prop.zp_encrypt && gbh_copies >= SPA_DVAS_PER_BP) + if (BP_IS_ENCRYPTED(bp) && gbh_copies >= SPA_DVAS_PER_BP) gbh_copies = SPA_DVAS_PER_BP - 1; int flags = METASLAB_HINTBP_FAVOR | METASLAB_GANG_HEADER; |