[libclc] Rework libclc naming convention to use the triple (#177465)
Summary:
Right now all these libraries are installed in the `libclc/` directory
in the compiler's resource directory. We should instead follow the
per-target approach and install it according to the triple. The
sub-architectures will be put in a subdirectory as well.
I will do refactorings on this later to remove all the redundant targets
and pull this into common handling.
Also we should accept `--libclc-lib` without an argument to just find it
by default. I don't know what the plan here is since AMDGCN is the only
triple that uses this flag.
acpi_spmc: Add system power management controller driver
Add SPMC (system power management controller) driver as acpi_spmc. This
is the device which provides the LPI device D-state constraints and
allows for OSPM to send S0ix/modern standby entry/exit notifications.
This supports the original Intel DSM
(https://uefi.org/sites/default/files/resources/Intel_ACPI_Low_Power_S0_Idle.pdf,
untested), the AMD DSM (tested), and the Microsoft DSM (tested).
Before entry, acpi_spmc_check_constraints is called to notify of any
violated power constraints. This will use acpi_pwr_get_state to get
current device D-states when that gets added back.
Reviewed by: olce
Tested by: jkim, Oleksandr Kryvulia, Matthias Lanter
Approved by: olce
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D48387
NAS-139463 / 26.04 / fix false negative on service reload (#18096)
Our CI has been failing sporadically because of false negative service
state reporting after reload operations.
On a machine where this occurred, this is what was in the logs.
```
[2026/01/26 00:13:47] (WARNING) middlewared.plugins.service_.services.base.call_unit_action_and_wait():298 - ssh.service Reload job finished with result: invalid
[2026/01/26 00:13:47] (ERROR) ServiceService.reload():356 - Service 'ssh' not running after reload
```
SSH service was actually running fine. The result: invalid occurs when a
systemd job is superseded (common with "replace" mode), but the service
itself is healthy.
Changes:
1. Renamed _verify_service_started → _verify_service_running and
extended to handle Reload actions:
- Start/Restart: accepts active or activating
[4 lines not shown]
NAS-139445 / 25.10.2 / Add validation checks for adding the root user to groups (by mgrimesix) (#18097)
The root user can be a member of 'builtin_administrators' only and
cannot be added to other groups.
We are missing validation checks for this in the group management
interface.
This PR adds the validation checks to the group management interface to
block adding root to other groups.
Also added a CI test.
Original PR: https://github.com/truenas/middleware/pull/18095
Co-authored-by: Mark Grimes <mark.grimes at ixsystems.com>
NAS-139445 / 25.10.3 / Add validation checks for adding the root user to groups (#18095)
The root user can be a member of 'builtin_administrators' only and
cannot be added to other groups.
We are missing validation checks for this in the group management
interface.
This PR adds the validation checks to the group management interface to
block adding root to other groups.
Also added a CI test.
Firewall: Aliases - expire geoip aliases when there's either no database installed or its newer than the alias contents populated. closes https://github.com/opnsense/core/issues/9374
In the long run we should probably refactor the alias class so different types can have their own implementations, but this has a lot more impact than injecting a specific expire() implementation for geoip information at its current spot.
The additional advantage of this change is it will update aliases before their TTL expires when the geoip database is newer than the alias content.
(cherry picked from commit 7bb40089867079e75857823d26ecdee5b12075d8)
[AMDGPU] Add FeatureGFX13 and SMEM encoding for gfx13 (#177567)
For now list of features is based on gfx12 and gfx1250
---------
Co-authored-by: Jay Foad <jay.foad at amd.com>
[X86] combineConcatVectorOps - concat(scalar_to_vector(extractelt(x,0)),scalar_to_vector(extractelt(y,0))) -> concat(x,y) (#177930)
Peek through free scalar_to_vector/extract_vector_elt pairs (of the same
vector width) that might still persist (ideally a better topological
sorting would have removed these already....)
[clang][bytecode] Relax assertions in Pointer::{begin,end}Lifetime (#177906)
We could get here for array roots, for which the assertion doesn't
necessarily hold.
[AMDGPU][NFC] Refine the representation of MODE register values. (#177574)
- Eliminate the field masks.
- Segregate the encoding logic.
- Simplify and clarify the user code.
This is supposed to help updating downstream branches where we
have a more advanced version of the same facility.
interfaces: generalise the dhcp6c_script using the new IFNAME variable #7647
The file was conceptually created in d36f0f4f62557 and before was a single
command line script... so add appropriate copyrights from that time onward.
Many thanks to Martin for pinoeering this back in the day!
interfaces: show the prefix shift in the log message
Move the other force message to the respective if which is more or
less what we had before. This is important for making clear what
the impact of #9521 to renewals actually is.
interfaces: missed script path via @cm-rudolph
interfaces: multi-dhcp6c support and custom PD association #7647
This splits off rtsold and dhcp6c into separate processes
which frees us from the restrictions of faked iterative IDs
for PD associations. For NA we simply default to 0 now.
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
Add two debugging files which still need to be steered via the
debug setting.
[Clang] prevent assertion in __has_embed parameter recovery at end-of-directive (#175104)
Fixes #175088
---
This PR addresses an assertion failure in the preprocessor triggered
when `__has_embed` parameter parsing reaches end-of-directive while
expecting a parenthesized argument.
fix setting DMA base addresses of iwn(4) Tx rings 17 and beyond
For Tx rings 17 and up, the driver was writing DMA base addresses
to the wrong registers. The firmware would crash when we tried to
use those rings.
This was never noticed before because those rings had never been
used by the driver until the recent introduction of support for
DSCP_EF in the wireless stack.
Use of Tx ring 17 in iwn is triggered by DSCP_EF, which the stack
is now mapping to TID 6, which the iwn code maps to queue index 16,
which addresses the 17th ring.
This issue only affected iwn 5000/6000 series devices. The earlier
devices only have 16 Tx rings and the driver respects that limit.
fatal firmware errors reported by + fix tested + ok bluhm@
