[Flang][NFC] Remove unnecessary template instantiations (#239182)
Since #216960, the `Expr<>` specializations are not partial
specializations anymore, hence they do not need explicit instantiations
that tell the compiler which instances it needs to instantiate. Remove
the explicit instantiations that do nothing. Some other explicit
instantiations were unnecessary even before #216960.
Suggested by @eugeneepshteyn
(https://github.com/llvm/llvm-project/pull/238748#discussion_r4468788352)
games/freeciv: update to 3.2.7 release (+)
FreeCiv-3.2.7 is a generic bugfix release in the freeciv-3.2 series.
Release notes: https://freeciv.fandom.com/wiki/NEWS-3.2.7
translate-toolkit: updated to 3.20.4
3.20.4
This release improves translation key validation and fixes Nextcloud
JSON fallbacks for untranslated strings.
when getnetby*(3) family were refactored by schwarze in 2018 as a
wrapper on gethostby*(3), the ip address in the structure was
mistakenly considered a pointer to an ip address, and a dereference
was attempted. The long survival of this bug tells us that
getnetby*(3) is used extremely rarely. In fact it was noticed by
afresh1@ on a strict-alignment architecture which inspected a HOST
with an odd ip address (byte order can also matter)
ok millert
openvpn: updated to 2.7.9
2.7.9
Security fixes
- win32: restrict loading plugin dependencies (DLLs) to plugin, app
and system directories.
- win32: run openvpn.exe from the interactive service at "high integrity
level", that is, process memory of openvpn.exe and all its threads are
protected from tampering. Signals/Events are still permitted.
- win32: openvpnserv: strictly filter user-defined environment variables
before passing to openvpn.exe (CVE-2026-121720)
- win32: openvpnserv: make validation of openvpn command line more robust
to invalid-quoting attacks (CVE-2026-115342)
[63 lines not shown]
Services: Kea DHCPv4: Add a simple shared_networks option to subnets (#11115)
Subnets can now select an interface, subnets with the same interface will be put into a shared network.
This means its not decided by the interface IP of the receiving interface anymore, but by a mandatory client-classes membership
which is decided by matching a single DHCP option of the users choice as the gatekeeper to the subnet.
This way, multiple subnets can be served from the same interface.
[libc++][pstl] Add serial implementations of partitioning algorithms to PSTL (#234598)
This PR adds serial implementations of the partitioning algorithms to
PSTL.
They are added to the serial backend only, such that any other backend
can fall back to these implementations.
Currently there's no intent to provide parallel versions of these
algorithms, but later they can be added as well.
These are the added algorithms:
- `std::partition`
- `std::stable_partition`
- `std::partition_copy`
Included tests check that:
- Semantics of the functions is correct.
- The functions correctly SFINAE out when the first argument is not an
execution policy.
- The `nodiscard` policy is followed.
[3 lines not shown]
[LoongArch] Fix misaligned frame-index offset for vldrepl.{h,w,d} (#239516)
eliminateFrameIndex did not check that the final offset is a multiple of
the access size for [X]VLDREPL_{H,W,D}, so a byte-aligned stack object
could produce an unencodable immediate. Materialize the address in a
scratch register in that case, as is already done for [X]VSTELM_*.
Assisted-by: LLM
Fixes #239508
[AArch64] Prevent outlining when PAuthLR attributes do not match (#238788)
Adds outliningCandidatesPAuthLRConsensus to ensure that both candidates
use the same method for return address signing when Feat_PAuth_LR is
enabled to be considered for outlining.
When outlining is allowed, also ensure that the branch-protection-pauth-lr
attribute is copied.
[Remarks] Make YAML remark arguments round-trip
The remark serializer writes an argument value with more than one
newline as a literal block scalar. A block scalar has no escapes, so a
value that also held a control character was written with the raw byte,
which strict YAML readers reject. Output::blockScalarString now falls
back to a double-quoted scalar when a literal block cannot hold the
value: a non-printable character (C1 controls, and NEL, LS and PS,
which YAML 1.1 readers take as line breaks), a carriage return, or a
first line that starts with a space. Input accepts either form.
The remark parser took the raw scalar text and stripped only single
quotes, so double-quoted values came back with their quotes and
escapes. Decode keys and values with ScalarNode::getValue and report
escape errors; the serializer quotes keys such as INST_@ too. Reject
strings that decode to a NUL, since the bitstream string table stores
NUL-terminated strings.
Output::blockScalarString always wrote "|", which keeps exactly one
[4 lines not shown]
www/immich: Update to 3.3.6
The release only touches the machine learning side, the server carries the
new version number. The build kit returns to the plain version; the
revision it carried was for the geodata file that the kit script now fetches
on its own.
Changelog: https://github.com/immich-app/immich/releases/tag/v3.3.6
Sponsored by: Netzkommune GmbH
www/immich-ml: Update to 3.3.6
Upstream turns onnxruntime telemetry off, which a recent onnxruntime release
had enabled by default. This port never sent anything: misc/py-onnxruntime
builds with telemetry off, and the generic implementation outside Windows is
a stub that reports itself disabled. The guard upstream added is harmless
here.
Changelog: https://github.com/immich-app/immich/releases/tag/v3.3.6
Sponsored by: Netzkommune GmbH
NAS-145079 / 27.0.0 / Release NFS locks before unmounting a dataset (by ixhamza) (#20146)
### Background
nfsd and lockd keep a file open for every NFSv3 lock and every NFSv4
open or delegation, and deleting a share does not release them. Once the
share is gone, an NFSv3 client can't even release a write lock anymore:
lockd reopens the file through nfsd for the unlock, and the handle is
stale by then. The dataset stays busy, so `pool.dataset.delete`,
`pool.dataset.lock` and `pool.export` fail with EBUSY, even after a lazy
unmount has hidden it. We saw this on a customer system weeks after the
shares had been deleted.
### Change
A private `nfs.release_dataset_filesystems` that the three operations
call right before they unmount. For every live filesystem in the tree it
writes `/proc/fs/nfsd/unlock_filesystem`, reaching the filesystem
through `fsmount()` so a lazily unmounted one works too, and does the
same for snapshots automounted under `.zfs/snapshot`. This releases
NFSv3 locks and NFSv4 opens and delegations. A filesystem another share
[26 lines not shown]
NAS-145079 / 27.1.0 / Release NFS locks before unmounting a dataset (by ixhamza) (#20147)
### Background
nfsd and lockd keep a file open for every NFSv3 lock and every NFSv4
open or delegation, and deleting a share does not release them. Once the
share is gone, an NFSv3 client can't even release a write lock anymore:
lockd reopens the file through nfsd for the unlock, and the handle is
stale by then. The dataset stays busy, so `pool.dataset.delete`,
`pool.dataset.lock` and `pool.export` fail with EBUSY, even after a lazy
unmount has hidden it. We saw this on a customer system weeks after the
shares had been deleted.
### Change
A private `nfs.release_dataset_filesystems` that the three operations
call right before they unmount. For every live filesystem in the tree it
writes `/proc/fs/nfsd/unlock_filesystem`, reaching the filesystem
through `fsmount()` so a lazily unmounted one works too, and does the
same for snapshots automounted under `.zfs/snapshot`. This releases
NFSv3 locks and NFSv4 opens and delegations. A filesystem another share
[26 lines not shown]
[FixIrreducible] Do not redirect unreachable edges to non-entry blocks (#239557)
Attempting to redirect these edges broke the CFG and caused either
assertion failures or dominance verification failures.
This was previously fixed in 0b4cf802fad4 but the fix was lost in the
rewrite fa4cc9ddd58e.
