NAS-141988 / 25.10.6 / Move remote disk retaste call in failover event (by yocalebo) (by bugclerk) (by bugclerk) (#19429)
There is no reason that this remote call should be ran before we import
the zpool. This is sending a request to the remote controller on an HA
system and who knows what state it's in at the time we make the request.
The point is that it should never delay or block the importing of the
zpool on the master event.
This does 3 things:
1. move the remote call to outside the "critical" failover section to
prevent unnecessary delays in restoring services in a failover event
2. fix the logging messages to be persistent
3. add the `job: "RETURN"` argument to `failover.call_remote` so we do
not wait for this to complete at all. We just fire and forget
Original PR: https://github.com/truenas/middleware/pull/19426
Original PR: https://github.com/truenas/middleware/pull/19427
[4 lines not shown]
[CIR] Accept __int128 in x86_64 calling-convention lowering (#211142)
The x86_64 calling-convention bridge rejected every integer wider than 64
bits, so a function taking or returning `__int128` hit `errorNYI` even though
its ABI treatment is simple.
On x86_64 `__int128` is Direct and passes in a pair of integer registers,
matching an i128 argument or return in classic CodeGen. `isSupportedType` now
accepts non-bitint integers of width 128 alongside the register-sized widths.
A struct holding a single `__int128` is exactly two eightbytes, so it reaches
the aggregate path and is Direct-coerced to i128; a struct spanning more than
two eightbytes stays Indirect (byval/sret).
`_BitInt` stays rejected pending its register-pair coercion and padding
handling, including `_BitInt(128)`. Non-C intermediate widths (65..127) stay
rejected too: the scalar Direct branch would pass them through unchanged,
without the register-pair coercion they would need.
NAS-141988 / 26.0.0-BETA.3 / Move remote disk retaste call in failover event (by yocalebo) (by bugclerk) (#19428)
There is no reason that this remote call should be ran before we import
the zpool. This is sending a request to the remote controller on an HA
system and who knows what state it's in at the time we make the request.
The point is that it should never delay or block the importing of the
zpool on the master event.
This does 3 things:
1. move the remote call to outside the "critical" failover section to
prevent unnecessary delays in restoring services in a failover event
2. fix the logging messages to be persistent
3. add the `job: "RETURN"` argument to `failover.call_remote` so we do
not wait for this to complete at all. We just fire and forget
Original PR: https://github.com/truenas/middleware/pull/19426
Original PR: https://github.com/truenas/middleware/pull/19427
[3 lines not shown]
NAS-141988 / 26.0.0-RC.1 / Move remote disk retaste call in failover event (by yocalebo) (#19427)
There is no reason that this remote call should be ran before we import
the zpool. This is sending a request to the remote controller on an HA
system and who knows what state it's in at the time we make the request.
The point is that it should never delay or block the importing of the
zpool on the master event.
This does 3 things:
1. move the remote call to outside the "critical" failover section to
prevent unnecessary delays in restoring services in a failover event
2. fix the logging messages to be persistent
3. add the `job: "RETURN"` argument to `failover.call_remote` so we do
not wait for this to complete at all. We just fire and forget
Original PR: https://github.com/truenas/middleware/pull/19426
---------
Co-authored-by: caleb <yocalebo at gmail.com>
NAS-141988 / 27.0.0-BETA.1 / Move remote disk retaste call in failover event (#19426)
There is no reason that this remote call should be ran before we import
the zpool. This is sending a request to the remote controller on an HA
system and who knows what state it's in at the time we make the request.
The point is that it should never delay or block the importing of the
zpool on the master event.
This does 3 things:
1. move the remote call to outside the "critical" failover section to
prevent unnecessary delays in restoring services in a failover event
2. fix the logging messages to be persistent
3. add the `job: "RETURN"` argument to `failover.call_remote` so we do
not wait for this to complete at all. We just fire and forget
[NFC][VPlan] Add initial tests for future VPlan-based stride MV (#182594)
I tried to include both the features that current
LoopAccessAnalysis-based transformation supports (e.g., trunc/sext of
stride) but also cases where the current implementation behaves poorly,
e.g., https://godbolt.org/z/h31c3zKxK; as well as some other potentially
interesting scenarios I could imagine.
The are two test files with the same content. One is for VPlan dump
change of the future transformation alone (I'll update
`-vplan-print-after` in the next PR), another is for the full vectorizer
pipeline. The latter has two `RUN:` lines:
* No multiversioning, so the next PR diff can show the transformation
itself
* Stride multiversionin performed in LAA, so that we can compare next
PR's
VPlan-based transformation vs old behavior.
suitesparse: update to 7.12.3
* CHOLMOD 5.3.5: typo in user guide; minor revision to API in
cholmod.h
* ParU 1.1.1: MATLAB mexFunction does not #include mkl.h on Intel
systems
* GraphBLAS 10.3.2: minor update for recent clang compilers
* LAGraph 1.2.2: minor update for MSVC compiler (with no stdalign.h)
* SuiteSparse_config 7.12.3: version update to match SuiteSparse.
* CSparse 4.4.2: minor fix to build system; sync version with
CXSparse
* UMFPACK 6.3.8: sync definition and declaration of umf_row_search.
[test] Use temp directory for output (#212379)
Test was added in #208072
Some test environment run tests in a readonly directory. Writing is only
allowed in temp directory.
[mlir] Make lit site configs relocatable (#212406)
Follow the same pattern as all the other test suites where the PATHS
option to configure_lit_site_cfg and the path() function in the lit site
config are used to make site configs relocatable.
NAS-141946 / 26.0.0-BETA.3 / Fix AD member-server breakage on HA failover and upgrade (by anodos325) (#19424)
Fix two AD member server issues:
1. After initial AD setup on TrueNAS HA, winbindd can end up running
with a stale cached domain SID that no longer matches what the rpc SAMR
service accepts. This leads to local-alias expansion in group tokens
failing with `NT_STATUS_NO_SUCH_DOMAIN` and failure to generate full
group list when doing privilege checks. It self-resolves after a second
failover event.
2. On upgrade the new boot environment has an empty secrets.tdb. Machine
account restore can race with a periodic keytab check, and if it loses
(keytab check comes first), the periodic keytab check can backup the
incomplete secrets.tdb over the good database copy, destroying the
stored machine account secret.
Changes:
[23 lines not shown]
NAS-141946 / 26.0.0-RC.1 / Fix AD member-server breakage on HA failover and upgrade (by anodos325) (#19425)
Fix two AD member server issues:
1. After initial AD setup on TrueNAS HA, winbindd can end up running
with a stale cached domain SID that no longer matches what the rpc SAMR
service accepts. This leads to local-alias expansion in group tokens
failing with `NT_STATUS_NO_SUCH_DOMAIN` and failure to generate full
group list when doing privilege checks. It self-resolves after a second
failover event.
2. On upgrade the new boot environment has an empty secrets.tdb. Machine
account restore can race with a periodic keytab check, and if it loses
(keytab check comes first), the periodic keytab check can backup the
incomplete secrets.tdb over the good database copy, destroying the
stored machine account secret.
Changes:
[23 lines not shown]
[llvm-objcopy] Address review feedback for AMDGPU test in cross-arch-headers
Per reviewer feedback, use the existing non-AMDGPU input (%t.o, EM_NONE)
to test conversion to elf64-amdgpu. This properly demonstrates that
--output-format changes the machine type, consistent with all other cases
in this test file.
The output reports Arch: unknown because converting from a non-AMDGPU ELF
produces e_flags=0 (no EF_AMDGPU_MACH set); added a comment explaining
this. Flag control is a separate concern for a follow-on PR.
[libc++] Reduce sequence container benchmark size ladder (#212281)
The sequence containers were registered for 32, 1024 and 8192. This
patch drops the mid-size point to get roughly a 30% speedup when running
the benchmarks.
[libc++] Drop char8_t instantiation from string benchmarks (#212283)
The string benchmarks instantiated every benchmark for char, char8_t and
wchar_t. char8_t exercises the same code paths as char, so drop it to
get roughly a 30% speedup on this benchmark time.
NAS-141946 / 27.0.0-BETA.1 / Fix AD member-server breakage on HA failover and upgrade (#19399)
Fix two AD member server issues:
1. After initial AD setup on TrueNAS HA, winbindd can end up running
with a stale cached domain SID that no longer matches what the rpc SAMR
service accepts. This leads to local-alias expansion in group tokens
failing with `NT_STATUS_NO_SUCH_DOMAIN` and failure to generate full
group list when doing privilege checks. It self-resolves after a second
failover event.
2. On upgrade the new boot environment has an empty secrets.tdb. Machine
account restore can race with a periodic keytab check, and if it loses
(keytab check comes first), the periodic keytab check can backup the
incomplete secrets.tdb over the good database copy, destroying the
stored machine account secret.
Changes:
[17 lines not shown]
[libc++] Defer removal of two escape hatches to LLVM 25 (#211553)
Rather than removing the escape hatches for trivially default
constructible allocator and bitset's const reference type in LLVM 24,
keep them around for another release since they have not been widely
deployed yet.
