security/openvpn-devel: Update to commit 22a24132da
This brings in the upstream development work of the last two months,
including two CVE fixes relevant for all platforms.
One of the bundled patch files was adjusted to take into account
upstream formatting changes on tests/t_cltsrv.sh.
PR: 298286
Approved by: osa, vvd (Mentors, implicit)
MFH: 2026Q3
Security: CVE-2026-84790
Security: CVE-2026-84732
(cherry picked from commit 15c68d3c519680f8e624112270f923a060f08e3b)
security/openvpn-devel: Update to commit 22a24132da
This brings in the upstream development work of the last two months,
including two CVE fixes relevant for all platforms.
One of the bundled patch files was adjusted to take into account
upstream formatting changes on tests/t_cltsrv.sh.
PR: 298286
Approved by: osa, vvd (Mentors, implicit)
MFH: 2026Q3
Security: CVE-2026-84790
Security: CVE-2026-84732
Revert "[CodeGen] Use RegisterClassInfo for remaining allocation-order users" (#221749)
Reverts llvm/llvm-project#216510
breaks tests MIOpen/CK shard 1-4 in CI
queueing this up in case we want to save a bit of time
[SCEV] Add test coverage for ext-nusw/nsuw inference (#218943)
Complete the existing incorrect-nsw test, showing that zext-addrec nusw
is not implied by nw on the pre-inc AR, and that sext-addrec nsuw is not
implied by nw on the pre-inc AR. See also: #217405 and #217362.
Assisted-by: AI
vp_crossmp: weaken the assert and make it more precise
Since the vp_crossmp vnode can leak into vn_vptocnp() calls due to
nullfs file mounting, not all lock requests are non-sleeping. The
requirement for the crossmp locking is that all lock requests should be
shared. Then, it does not matter if the requests allow sleeping, since
all locks are shared.
Also, check the lock type by correctly masking it with LK_TYPE_MASK.
Reported and tested by: pho
Reviewed by: jah, markj
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D59468
audio/shairport-sync: Update to 5.5
* Update to 5.5
* Enable SNDIO by default
* Remove incorrect SNDIO deprecation notice
* Add guidance for selecting the sndio output device on FreeBSD
The sndio backend is supported upstream and should not be confused with
the deprecated soundio backend.
On FreeBSD, sndio's default device does not necessarily correspond to
the default sound device reported by /dev/sndstat. Add a conditional
pkg-message with guidance for explicitly selecting the desired device.
[offload][omp] Remove data_fence
All supported backends execute enqueued work on a given queue in
submission order (CUDA, AMDGPU, and Host queues are always in-order;
Level Zero's default and non-default in-order/synchronous command
modes are as well), so the explicit data-fence used to order a
pointer-attachment after prior data transfers is unnecessary. Remove
the DeviceTy/GenericDeviceTy/GenericPluginTy dataFence chain and the
now-unused olQueueBarrier liboffload API added to support it.
[SimplifyCFG] Preserve !unpredictable when forming a switch (#221580)
SimplifyCFG turns a chain of equality comparisons into a switch in two
places, performValueComparisonIntoPredecessorFolding() and
simplifyBranchOnICmpChain(), and neither propagated !unpredictable. The
hint was therefore dropped even though it is valid on a switch and the
reverse transform, simplifySwitchOfCmpIntrinsic(), already preserves it.
Propagate the metadata in both. Folding a comparison into a predecessor
merges two decisions into a single switch, so the result is only marked
unpredictable when both of the folded comparisons were. That also makes
chains longer than two blocks work: the fold runs once per predecessor
and reads the metadata back off the switch it built on the previous
iteration.
simplifyBranchOnICmpChain() also emits a range check instead of a switch
when the case values are contiguous. That branch is an exact replacement
for the original one, so it inherits the metadata unconditionally, and
the flag now survives into the machine IR.
Fixes #42658.
sysctl.7: add a kern.entropy.* reference to summary table
(Where sub-nodes are a mix of writable and non-writable, the convention
appears to be "yes" in summary, which makes the most sense, so
following suit.)
