NAS-139542 / 25.10.2 / In become_active ensure all user-related config (by anodos325) (#18126)
This commit ensures that when a controller becomes active, we regenerate
the user and API key configuration so that there's no chance of stale
information being preset.
Original PR: https://github.com/truenas/middleware/pull/18125
---------
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
NAS-139542 / 25.10.2 / In become_active ensure all user-related config (by anodos325) (#18126)
This commit ensures that when a controller becomes active, we regenerate
the user and API key configuration so that there's no chance of stale
information being preset.
Original PR: https://github.com/truenas/middleware/pull/18125
---------
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
NAS-139542 / 26.0.0-BETA.1 / In become_active ensure all user-related config (#18125)
This commit ensures that when a controller becomes active, we regenerate
the user and API key configuration so that there's no chance of stale
information being preset.
[VectorCombine] Fix crash with poison mask elements in shrinkLoadForShuffles (#178920)
## Summary
Fixes assertion failure when `shrinkLoadForShuffles` processes shuffle
masks containing poison elements.
The bug was introduced in #149093 , when adjusting mask indices for load
trimming, poison indices (-1) were modified to invalid values (e.g.,
-2), causing `isSingleSourceMaskImpl` to assert.
The fix preserves poison indices without modification.
Fixes #178917
## Test plan
- Added regression test `@shuffle_with_poison_mask`
[lldb] Add FP conversion instructions to IR interpreter (#175292)
This allows expressions that use these conversions to be executed when
JIT is not available.
yt-dlp-ejs: update to 0.4.0.
Remove build dependency on node; add lock for every package manager by @Grub4K in #38
Documentation and CI improvements by @bashonly in #39
Fix windows build with bun and wrapper files by @Grub4K in #41
Harden CI/CD pipeline by @bashonly in #40
Fix sig extraction in tce variant of player c1c87fb0 by @Grub4K in #43
In become_active ensure all user-related config
This commit ensures that when a controller becomes active, we
regenerate the user and API key configuration so that there's
no chance of stale information being preset.
[ThinLTO] Clear read/write only flags when referencing function summary (#178761)
Conservatively clear read/write only flags during attribute propagation
across all of a ValueInfo's summaries when one is a function summary.
While function summaries will not be read/write-only, we need to ensure
that
any global variable summary with the same GUID/ValueInfo is also not
marked
read or write only. This case can occur with same named locals in
different
modules compiled without enough path.
Enhance the current test to confirm this works correctly for a couple
cases.
This change enables a follow on simplification and compile time
improvement
during importing of global variables.
[clang][analyzer]Add TaintPropagation:EnableDefaultConfig config parameter (#176185)
The new optin.taint.TaintPropagation:EnableDefaultConfig checker
configuration parameter makes it possible for the users to disable the
built-in taint configuration and use a full custom configuration
instead.
ktrcsw(): should not be called when the thread is owning interlock or on sleepq
The issue is that for ktrcsw() we lock the ktrace_mtx mutex while owning
the interlock from a subsystem that called msleep(). In particular, the
VM subsystem might call msleep() if page allocation failed. This
establishes order VM locks (e.g. domain free queue lock) -> ktrace_mtx.
Calling free() while owning ktrace_mtx gives the reverse order.
Worse, msleep_spin_sbt() call s ktrcsw() while the thread is put on
sleep queue. Then, since the mutex might be contested, the thread needs
to be put on turnstil, which cannot work.
Move the ktrcsw() call for switch-out after the wakeup, when the thread
does not yet re-obtained any locks. From there, we call a special
version of ktrcsw(), which is passed the actual time when the context
switch occured.
The drawback is that the switch-out record is only written in the
ktrace.out file after the switch-in occurred, but this is probably not
[7 lines not shown]
ktrcsw(): should not be called when the thread is owning interlock or on sleepq
The issue is that for ktrcsw() we lock the ktrace_mtx mutex while owning
the interlock from a subsystem that called msleep(). In particular, the
VM subsystem might call msleep() if page allocation failed. This
establishes order VM locks (e.g. domain free queue lock) -> ktrace_mtx.
Calling free() while owning ktrace_mtx gives the reverse order.
Worse, msleep_spin_sbt() call s ktrcsw() while the thread is put on
sleep queue. Then, since the mutex might be contested, the thread needs
to be put on turnstil, which cannot work.
Move the ktrcsw() call for switch-out after the wakeup, when the thread
does not yet re-obtained any locks. From there, we call a special
version of ktrcsw(), which is passed the actual time when the context
switch occured.
The drawback is that the switch-out record is only written in the
ktrace.out file after the switch-in occurred, but this is probably not
[7 lines not shown]
