CI: don't fail a passing job when a log reader has already exited
Once a VM's tests finish the runner kills that VM's log reader. If the
reader is already gone, kill reports ESRCH, and since the script runs
under set -eu that ends it and the job is reported failed after the
tests have already passed.
That is what turned the fedora44 run in
https://github.com/openzfs/zfs/actions/runs/30772421272 red:
vm1: Results Summary
vm1: PASS 1151
vm1: FAIL 2
vm1: SKIP 6
...
qemu-6-tests.sh: line 143: kill: (20700) - No such process
##[error]Process completed with exit code 1.
All 13 failures in that run were on the expected list and neither VM
[13 lines not shown]
CI: publish the per-VM test counter atomically
Each VM's log reader keeps a running test count in /tmp/ctr-vm$ID and
reads every other VM's counter to print the combined progress figure.
The counter is published with a plain redirect, which truncates the file
before it writes, so a reader can see it empty. `read` then returns 1,
and because the reader inherits set -eu that ends the reader subshell.
The VM keeps running and its results are recovered later from the
artifact, but its output stops being prefixed into the live log from
that point on, with nothing said about why.
Seen on fedora44 in
https://github.com/openzfs/zfs/actions/runs/30772421272. vm2's last
prefixed line is refreserv/cleanup at 01:57, carrying counter 745, while
vm1 keeps reporting vm2 frozen at 746 for the remaining 38 minutes: the
reader incremented the counter and died before printing that line. vm2
itself ran on until 02:14 and its 899/11/6 summary never reached the
live log.
[9 lines not shown]
[FileCheck] Avoid matching IR keywords in source filenames (#213809)
Anchor checks for declare, define, and comdat to the start of lines or another fixture so
paths in module headers cannot satisfy or invalidate them.
Tested with make check.
Assisted by AI.
science/InsightToolkit501: Remove expired port
2026-04-30 science/InsightToolkit501: Fails to build, error: no template named 'binary_function' in namespace 'std'
Batch object reallocation syncs in zfs receive
When an incremental stream reallocates an object at a different dnode
slot count, receive_object() must wait for the old dnode's free to
sync out before the object number can be claimed again, because
dnode_check_slots_free() only accepts slots whose final dirty txg has
synced. The receive writer did this with one txg_wait_synced() per
reallocated object, so a dataset that ever changed dnodesize (for
example dnodesize=auto, as the root-on-ZFS guides suggest) receives
such incrementals at a few KB/s while the pool syncs mostly empty
txgs (#11353).
Batch those waits. The frees are still issued immediately, since
many frees can share one txg, but the record whose claim would need
the sync is parked on a per-receive list and the affected dnode slot
ranges are tracked in a small AVL tree. Later records that touch a
parked range park behind it in stream order while unrelated records
keep flowing. Once the batch reaches zfs_recv_defer_batch_size
(default 32 MB, 0 restores the old behavior) or the stream ends, a
[38 lines not shown]
NAS-142059 / 27.0.0-BETA.1 / Directory services cache fixes (#19477)
insert_cache_entry() built the NAME_ key from the numeric id rather than
the name, so entries added by the lazy insertion path were only
reachable by id. A by-name lookup for such an entry missed the cache and
fell through to NSS plus idmap.synthetic_user. The bulk fill path was
unaffected, and query_cache_entries() reads only ID_-prefixed keys, so
enumeration results did not change.
DSCacheFill did not remove its temporary files when `fill_cache()`
raised `before _commit()`, so a failed fill can leave
`directory_service_cache_tmp_*` files behind in the cache `directory.
fill_cache()` documents NssError, WBCErr and job abort as reachable, and
nothing else removes those files. Cleanup now also covers a failure
partway through `__enter__`, which does not invoke `__exit__`.
expire_cache() now writes a timezone-aware UTC timestamp, matching
fill_cache() and check_cache_expired().
[6 lines not shown]
[SPIRV] Split wide shader PHIs before applying explicit supported types (#213806)
fixes #213802
Apply the maximum-vector-size rule before the explicit PHI legality
rules for type. This way if we see a size 16 vector we split it
beforehand.
In more precise words this preserves existing legality rules while
ensuring shader PHIs wider than four lanes are split first.
Assisted by Copilot (GPT 5.6 Sol)
[X86] LowerPARITY - use countMaxActiveBits to determine if representable as uint8_t. NFC. (#214056)
Much cleaner than using the MaskedValueIsZero check.
Fix i64 -> xor(i32,i32) parity stage comment as well.
NAS-141754 / 27.0.0-BETA.1 / Make ZFS deduplication incompatible with the PERFORMANCE tier (#19336)
Deduplicated datasets are excluded from tiering: they report a null
tier, and dataset_set_tier and rewrite_job_create reject them.
Enabling dedup (ON/VERIFY) is refused only when a dataset's data is on
the SPECIAL vdev, i.e. the PERFORMANCE tier (special_small_blocks > 0).
REGULAR datasets, volumes, and pools without a SPECIAL vdev may be
deduplicated freely.
[X86] Handle multi-use setcc in commuteSelect (#213645)
When a setcc condition is shared between multiple vselects,
commuteSelect previously bailed out due to the m_OneUse constraint.
Extend it to check all users of the setcc and, if they all benefit from
commuting, invert the condition once with ReplaceAllUsesOfValueWith and
swap all vselect operands.
This fixes a write-mask fusion regression where masked min/max
reductions produced unfused vminps + vmovaps {%k} instead of a single
write-masked vminps {%k}.
