[DWARFYAML] Declare `OffsetEntryCount` as `uint64_t` (#224631)
This prevents a potential multiplication overflow when `OffsetsSize` is
calculated and fixes an issue reported by a CodeQL scan.
interfaces: skip pfsync interface reconfiguration if peer unchanged (#10924)
also check if mtu actually changes before applying it on pfsync0
(cherry picked from commit 95f552b3d6b765b47b271441cb616ed1d6d61bc6)
ice(4): Fix link bringup on driver load
Patch adding Total Port Shutdown support incorrectly
handled a case when this feature was not enabled in the NVM.
When TPS bit is not set driver should apply link configuration
according to user settings and update the status. Those steps
were mistakenly omitted, while the state flag was still set
to prevent link renegotation and status update on first
attempt to bring interface up with ifconfig.
Signed-off-by: Krzysztof Galazka <krzysztof.galazka at intel.com>
Reported by: kbowling
Reviewed by: kbowling
Fixes: 0011cd9f8863 ("ice(4): Support Total Port Shutdown on E830 devices")
MFC after: 2 weeks
Sponsored by: Intel Corporation
Differential Revision: https://reviews.freebsd.org/D59578
ice(4): Fix link bringup on driver load
Patch adding Total Port Shutdown support incorrectly
handled a case when this feature was not enabled in the NVM.
When TPS bit is not set driver should apply link configuration
according to user settings and update the status. Those steps
were mistakenly omitted, while the state flag was still set
to prevent link renegotation and status update on first
attempt to bring interface up with ifconfig.
Signed-off-by: Krzysztof Galazka <krzysztof.galazka at intel.com>
Reported by: kbowling
Reviewed by: kbowling
Fixes: 0011cd9f8863 ("ice(4): Support Total Port Shutdown on E830 devices")
MFC after: 2 weeks
Sponsored by: Intel Corporation
Differential Revision: https://reviews.freebsd.org/D59578
[AArch64] Combine truncate(buildvector) -> buildvector (#223787)
If late in the pipeline we are left with truncate(buildvector), we can
generate the buildvector directly. This helps remove the xtn and can
lead to other simplification.
Keep a created resource whose key cannot be recorded
## Problem
`zfs.resource.create` destroyed the resource it had just created when its encryption key could not be written to the database. That only happens when the middleware database itself is failing, where the next operations fail too, and master never rolled back here. The rollback's destroy also queued a late ZFS event whose handler deletes key rows by name, so a quick retry under the same name could have its freshly written key row removed and lose the dataset's key at the next reboot or failover.
## Solution
Let the key-record failure propagate and keep the resource, as master did. The key is still recorded when the mount fails, so a mount failure no longer loses a generated key, and the docstring and tests are updated to match.
[GlobalISel] Support GISelValueTracking for G_FREEZE. (#223696)
Port the SDAG FREEZE handling to GlobalISel. Look through G_FREEZE in
computeKnownBits, computeNumSignBits, and computeKnownFPClass when the
source is guaranteed not undef or poison.
Part of #150515.
---------
Co-authored-by: Matt Arsenault <arsenm2 at gmail.com>
[AMDGPU] Fix missed WMMA C-operand co-exec hazard
The gfx1250 WMMA co-execution hazard check treats only A, B and the
SWMMAC index as registers the in-flight MMA still reads. C (src2 of a
non-SWMMAC WMMA) is missing, so a VALU scheduled into the MMA's shadow
can clobber C and the MMA consumes the new value.
This is latent while C is tied to vdst, since the existing D check then
covers it. It miscompiles where the tie does not hold: for
v_wmma_bf16f32_16x16x32_bf16, whose D is narrower than C, and for the
_threeaddr form of any WMMA.
Add src2 to the checked set for non-SWMMAC WMMAs.
Drop the S3 service's status code from two docstrings
A reader of a dataset property check in middleware has no use for the
code the S3 service answers a client with. Both now say what the check
is for instead.
Fix mypy errors in the S3 bucket recovery
`bucket_dataset_properties` goes back to explicit keywords, which mypy
can check against each field's type, and the mapping a recover checks
against is read off it rather than the other way round.
The other three are a narrowing the render loop had left implicit, an
untyped NSS lookup, and OSError.errno being optional.
Add bucket recovery APIs
There are various situations in which we can have orphaned
buckets. Examples include:
* bucket is deleted and admin wants to reinstate.
* the NAS is disaster recovery instance and needs to activate
buckets after switching datasets to read-write.
This is facilited by inserting a .truenas_s3/config_backup.json
file inside each bucket (daemon-owned path) and restoring the
DB row / S3 config with some user-provided overrides if required.
Two new API endpoints are added:
* sharing.s3.recoverable_buckets lists mounted datasets containing
orphaned buckets.
* sharing.s3.recover basically takes a list of datasets and rebuilds
bucket configuration from backups for them.
gnuchess4: remove
This is the very old major version 4 of games/gnuchess,
imported over 20 years ago with no particular reason given.
No comment on pkgsrc-users.
[SLP] Add tests for affine loop address computations (NFC) (#226907)
Precommit tests for #226220: related affine address recurrences in a
loop whose index arithmetic SLP currently vectorizes and extracts per
lane for scalar loads and stores, which LSR would otherwise turn into
pointer increments.
`X86/strength-reducible-address.ll` has Haswell and skylake-avx512 RUN
lines. It covers strided loads, constant-offset GEPs, and a load/store
at the same address. The negative cases are loop-loaded offsets,
escaping addresses, and offsets computed in the preheader. The checks
are generated with current main.
sysutils/mirador: update to 1.19.1
1.19.1 - 2026-09-27
Fixed
The battery panel reads on NetBSD (#255). starship-battery 0.12.0 carries the fix for its NetBSD backend, which passed the kernel's plist buffer with the trailing NUL still on it and so parsed nothing. Diagnosed and confirmed on hardware by @0323pin; fixed upstream in starship/rust-battery#168. pkgsrc can drop its local patch.
Changed
A battery holding below full is now reported by the system rather than inferred. macOS says so directly once a charge limit is set, which starship-battery 0.12.0 surfaces as a state of its own; mirador had been reading it as "unknown, with no energy moving". The panel says PLUGGED IN either way, and the older inference stays for the platforms that still report it that way.
1.19.0 - 2026-09-24
Added
Arrange mode's keys can be changed (#284). An [arrange.keys] section moves any of them — the four moves, moving a whole row, keeping the arrangement, and picking another panel — and the legend shows the keys you chose. Esc still cancels and 1–9 still pick a panel. A key there may not also be a resize key, since resizing is read first. The key map on ? pressed twice lists the table, and reload and reset include it.
The panel and theme pickers' keys can be changed (#284). [panel_picker.keys] moves w's keys (the cursor, toggle, close) and [theme_picker.keys] moves t's (the cursor, keep, put_back), and each footer shows the key you chose. Esc always closes either picker. The theme picker's footer now draws Enter as ↵, as the rest of mirador does.
The help overlay's scroll keys can be changed (#284). [help_overlay.keys] moves up, down, page_up, page_down, first and last, and the overlay's footer shows the keys you chose. Any other key still closes it. None of them may be the help key, which opens the key map from there. With this, every key mirador reads comes from a table, except Ctrl+C, Esc and 1–9.
Fixed
[26 lines not shown]
