NAS-145288 / 27.1.0 / Reject numbers-only container names (by themylogin) (#20233)
The container name is used as a hostname, and glibc doesn't behave well
on numbers-only hostnames:
```
$ cat /etc/hosts
127.0.1.1 123
$ getent -s files hosts 123
0.0.0.123 123
```
Original PR: https://github.com/truenas/middleware/pull/20231
Co-authored-by: themylogin <themylogin at gmail.com>
[libc] Implement timerfd_(s|g)ettime on Linux. (#243657)
* Implement `timerfd_settime` and `timerfd_gettime` interface on Linux
platforms;
* These are simple syscall wrappers, with the caveat that we also use
`SYS_timerfd_(s|g)ettime64` on 32-bit platforms, if those are available
(RISCV-32).
* Adds a basic test case to validate relative/absolute timer behavior,
and reading
the number of expirations from the returned descriptor.
Assisted-by: Gemini, human-reviewed.
update to 1.30.7;
fixes the following vulnerabilities:
- use-after-free in resolver (CVE-2026-123634)
- memory corruption in HTTP/2 flow control (CVE-2026-123007)
- use-after-free in HTTP/3 (CVE-2026-121810)
- use-after-free in HTTP/2 (CVE-2026-123633)
- infinite loop while reading client request body over TLS 1.3 (CVE-2026-118899)
- use-after-free in mail proxy module (CVE-2026-113425)
- NULL pointer dereference when using PROXY protocol version 2 (CVE-2026-120993)
- buffer overflow when using alias with try_files (CVE-2026-125283)
- SNI bypass in client certificate validation in stream module (CVE-2026-120967)
- insufficient validation in stream ssl_preread module (CVE-2026-123640)
[LoongArch] Select [X]VADD.Q/[X]VSUB.Q for add/sub on vNi128 (#193912)
vNi128 types are not legal, so add/sub on them are expanded to scalar
add/sub with carry on GPRs. Combine them before type legalization into
new VADD_Q/VSUB_Q nodes on the equivalent i64 vector types, splitting
the vector into 256-bit parts with LASX and 128-bit parts for the rest.
Only do this when both operands are already in, or cheap to get into,
vector registers:
- simple loads with fast access whose other users can also use the value
in vector registers,
- bitcasts from vectors of LSX-legal element types that are not built
from GPRs,
- constants.
Loads are replaced with loads of the i64 vector type so that the loaded
value can be shared by other add/sub. Values in GPRs, such as function
arguments, keep using GPRs.
[4 lines not shown]
[LoongArch][NFC] Add tests for vector add on vNi128 (#193911)
Add tests for add/sub on vNi128 types with operands loaded from memory,
bitcast from vectors, constants and GPR arguments, as well as shared,
under-aligned, volatile and range-annotated loads, loads also used as
scalars, targets without unaligned access, and wider vectors.
Assisted-By: LLM
update to 1.30.7;
fixes the following vulnerabilities:
- use-after-free in resolver (CVE-2026-123634)
- memory corruption in HTTP/2 flow control (CVE-2026-123007)
- use-after-free in HTTP/3 (CVE-2026-121810)
- use-after-free in HTTP/2 (CVE-2026-123633)
- infinite loop while reading client request body over TLS 1.3 (CVE-2026-118899)
- use-after-free in mail proxy module (CVE-2026-113425)
- NULL pointer dereference when using PROXY protocol version 2 (CVE-2026-120993)
- buffer overflow when using alias with try_files (CVE-2026-125283)
- SNI bypass in client certificate validation in stream module (CVE-2026-120967)
- insufficient validation in stream ssl_preread module (CVE-2026-123640).
NAS-145310 / 28.0.0-BETA.1 / Hard-code SMB AAPL extensions, multichannel and streams on (by anodos325) (#20255)
Drop the DB columns and the logic that read them. The API fields stay
until the UI adapts; they read true and submitted values are ignored.
Original PR: https://github.com/truenas/middleware/pull/20253
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
[AArch64] CodeGen for STLP (#239588)
This patch lowers i128 aligned atomic release/seq_cst stores to STLP
instruction when FEAT_LSCP is present.
Codegen for LDAP and LDAPP will be added in the followup patch.
Depends on: #239556
[CIR] Diagnose failed initializer type adjustments (#234348)
Report the CIR initializer type whose conversion fails during recursive
layout adjustment, including active union members nested in structs and
arrays. Carry that type to the lowering operation so diagnostics
identify the unsupported initializer type even when the enclosing
storage type converts successfully.
Extend the initializer and language address space tests to check the
type-specific diagnostics while retaining coverage for inactive
unsupported members.
Assisted-by: Codex / GPT-6
[libsycl] Add sycl::half (#238751)
Adds sycl::half (SYCL 2020 4.14.1, Scalar data types), and
device::has/platform::has support for aspect::fp16 and aspect::fp64.
Design
Storage is _Float16 on host and device. Support of _Float16 on x86
arrived in LLVM 15, libsycl is built only with clang (kernel launch
integration) and won't support third-party host compilers. So using
native _Float16.
Defined in sycl::detail::half_impl, exposed as sycl::half. This keeps
argument-dependent lookup on a half argument limited to half's own
operators, as for float. Without it, once the SYCL built-in functions
exist, unqualified calls such as min(a, b) in code with using namespace
std would also find sycl::min and could become ambiguous.
Mixed-type operators are overloads for exact types, not a template. + -
* /, the comparisons and the compound assignments each have overloads
[15 lines not shown]
[InstCombine] Preserve !pcsections in mergeStoreIntoSuccessor (#243840)
mergeStoreIntoSuccessor creates a new store and copies only AA metadata,
access groups and DIAssignID, so the !pcsections of both stores was
lost. Give the merged store the union of both stores' !pcsections.
`!pcsections` metadata may be attached by any producer, including front
ends that emit it before IR optimizations. Preservation through IR
transformations remains best effort, as documented in
PCSectionsMetadata.md. This only fixes a place that already merges other
metadata kinds by hand (AA tags, access groups, DIAssignID) and dropped
!pcsections for no reason other than not being listed.
[Offload][L0] Move host memory pool ownership from L0DriverTy to plugin contexts (#236145)
In the L0 plugin, host allocations have two owners:
- `L0DriverTy` owns a host pool tied to the driver-wide `ze_context`.
This pool is used by libomptarget.
- Each `LevelZeroPluginContextTy` (created by `olCreateContext`) owns a
separate optional host pool through a `unique_ptr`, set up through the
first device's driver. If the context has no devices, there is no
device[0] to get the driver from, and so the allocator is never set up
and is left as `nullptr`.
Make every `LevelZeroPluginContextTy` own its host pool. This change is
intended to align the plugin with Level Zero semantics, where host
allocations are always tied to a context:
- `HostAllocator` is no longer optional, so it becomes a plain member
instead of a unique_ptr.
- The context borrows its `L0DriverTy` instead of just the raw L0
[8 lines not shown]
NAS-145310 / 27.1.0 / Hard-code SMB AAPL extensions, multichannel and streams on (#20253)
Drop the DB columns and the logic that read them. The API fields stay
until the UI adapts; they read true and submitted values are ignored.
(cherry picked from commit b2c110f1081b73328378014bd30d84b9f798de38)
[mlir][SPIR-V] Remove non local cluster size verification in GroupNonUniform ops (#214408)
The GroupNonUniform arithmetic and GroupNonUniformRotateKHR verifiers
followed the def-use chain of the cluster size operand, which MLIR
verifiers must not do and rejected valid modules using OpSpecConstant
for ClusterSize
[libc++][docs] Use Furo theme
Adopt the shared LLVM Furo configuration and wyvern logo, widen the content area on desktop viewports, and remove page-local contents directives that duplicate Furo's navigation.
LLM-aided
[MLIR][OpenMP] Support device shared memory for recipe ops
Some recipe ops (`omp.private` and `omp.declare_reduction`) can hold
stack allocations inside their allocation or initialization regions, and
these regions are inlined in the corresponding blocks of their users when
translating to LLVM IR.
The issue is that, when compiling for a target device, certain stack
allocations must be replaced with device shared memory to account for
the disjoint memory spaces of GPUs when kernels run in Generic mode.
This is sometimes handled by frontends by emitting `omp.alloc_shared_mem` and
`omp.free_shared_mem` operations instead of using stack allocations, and
the `StackToShared` MLIR pass addresses any remaining stack allocations
that need to be replaced.
None of those solutions are well suited for these recipe ops, which
might need to use device shared memory for some instantiations but not
others, based on context and usage of the resulting storage. Instead,
what this patch does is to identify the cases where device shared memory
[17 lines not shown]
[MLIR][OpenMP] Introduce a ReductionVarsInfo structure, NFC (#238363)
The MLIR to LLVM IR translation process for private and reduction
clauses is relatively similar, given that both are based on inlining
regions of a top-level template operation (`omp.private` and
`omp.declare_reduction`) pointed at by symbol, and mapping entry block
arguments to values as appropriate.
This similarity means that the same kind of information needs to be
passed around to helper translation functions. For privatization, this
is done using the `PrivateVarsInfo` structure but for reductions,
several vectors are passed instead.
This patch introduces a `ReductionVarsInfo` structure that mirrors the
existing `PrivateVarsInfo` to simplify the handling of this data and
converge on a similar pattern.
Assisted-by: Claude Opus 4.8
[MLIR][OpenMP] Refactor PrivateVarsInfo, NFC (#238362)
The `PrivateVarsInfo` structure holds, for each privatized variable,
multiple related values such as its corresponding MLIR entry block
argument, privatizer, etc. This is represented as a vector for each
property, which has the disadvantage of potentially getting out of sync
when new values aren't added to all vectors.
The proposed change is to create a nested structure holding the
information for a single variable and have `PrivateVarsInfo` hold a
vector of these structures. This prevents the previously mentioned issue
and also simplifies its use, as it no longer requires iterating in
lockstep over multiple vectors.
Assisted-by: Claude Opus 4.8
Internalize: Preserve the function analysis manager proxy
InternalizePass only changes the linkage, visibility and comdats of
globals which don't matter to any function analysis. Every function
analysis was discarded, including TargetTransformInfo. AMDGPU runs it
at the start of the pipeline for -amdgpu-internalize-symbols, but
CTMark does not. A sample of ROCm bitcode files improves by -0.09%
(geomean).
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[libc++][docs] Migrate feature status and macro tables to Markdown (#222065)
This is the third batch of changes to migrate libc++ documentation from
rst to markdown.
This covers the CSV tables, which are included into the markdown and
contain markdown markup. This involved some fairly ad-hoc removal of
reST space-escapes to minimize the pixel diff, but ultimately the
rendering diff is very minor.
Tracking issue: #201242
See the [migration guide] for more information.
[migration guide]:
https://llvm.org/docs/SphinxQuickstartTemplate.html#markdown-migration-guidelines
This is a stacked PR based on #222063, which will be a standalone commit
that
renames *.rst -> *.md before this PR lands for history preservation
purposes.
[libc++][docs] Rename generated feature-test documentation to Markdown (#222063)
Tracking issue: #201242
See the [migration guide] for more information.
[migration guide]:
https://llvm.org/docs/SphinxQuickstartTemplate.html#markdown-migration-guidelines
This is the initial straight rename commit. It will probably break the
docs build, but it has to be a separate PR for blame preservation
purposes.
NAS-145310 / 27.1.0 / Hard-code SMB AAPL extensions, multichannel and streams on (#20253)
Drop the DB columns and the logic that read them. The API fields stay
until the UI adapts; they read true and submitted values are ignored.
[IR] Keep !pcsections in dropUBImplyingAttrsAndMetadata (#243841)
!pcsections only requests that the instruction's PC be emitted into a
section; it does not imply undefined behavior. Dropping it when an
instruction is speculated, e.g. by SimplifyCFG store speculation, lost
the request for no reason.
[AsmPrinter] Skip !pcsections records whose auxiliary data was dropped (#243850)
Metadata does not keep globals alive, and ThinLTO function import does
not import globals that are referenced only from metadata. An imported
instruction whose !pcsections auxiliary tuple references such a global
ends up with a null operand, and emitPCSections crashed dereferencing
it.
Omit the records of a section whose auxiliary data was dropped, rather
than crashing or emitting the records without it. Other sections of the
same node are unaffected.
Only dropped (null) constants are skipped; otherwise malformed auxiliary
data still asserts.