NAS-141131 / 26.0.0-RC.1 / Set PARALLEL_SHUTDOWN for faster guest shutdown (by Qubad786) (#19001)
## Problem
On shutdown/reboot, TrueNAS stops containers and VMs one at a time,
waiting up to the per-guest shutdown timeout (90s by default) for each.
With many guests, this serializes into a long wait — a system with 10
containers and 10 VMs can spend most of its shutdown idle, waiting on
guests one after another.
## Solution
Set `PARALLEL_SHUTDOWN` in `/etc/default/libvirt-guests` so all
containers shut down concurrently and all VMs shut down concurrently.
The per-guest timeout is unchanged; the waits just happen in parallel.
libvirt applies `PARALLEL_SHUTDOWN` independently per URI (lxc, qemu),
so the cap only needs to cover the larger batch — hence
`max(len(containers), len(vms), 1)`.
[4 lines not shown]
Add --fn flag to llvm-lit to inject select-function pass into opt pipelines
Translates --fn=fn0,fn1 into -passes='select-function<fn=fn0;fn=fn1>,...'
by rewriting -passes= arguments in RUN lines after substitution.
Handles both single and double quoted pass pipelines.
Add select-function pass to keep only specified functions and their dependencies
Chains InternalizePass, GlobalDCEPass, and StripDeadPrototypesPass to
remove everything not transitively reachable from the selected functions.
Supports multiple roots via select-function<fn=foo;fn=bar>.
Merge tag 'v7.1-rc5-ksmbd-server-fixes' of git://git.samba.org/ksmbd
Pull smb server fixes from Steve French:
- fix for creating tmpfiles
- fix durable reconnect error path
- validate SID in security descriptor when inheriting DACL
* tag 'v7.1-rc5-ksmbd-server-fixes' of git://git.samba.org/ksmbd:
smb/server: promote S_DEL_ON_CLS to S_DEL_PENDING when close
ksmbd: validate SID in parent security descriptor during ACL inheritance
ksmbd: fix durable reconnect error path file lifetime
Merge tag 'for-7.1-rc4-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
Pull btrfs fixes from David Sterba:
"A batch of fixes to simple quotas:
- add conditional rescheduling point not dependent on the lock during
inode iterations to avoid delays with PREEMPT_NONE enabled
- fix subvolume deletion so it does not break the squota invariants
- properly handle enabling squota, tracking extents in the initial
transaction
- catch and warn about underflows, clamp to zero to avoid further
problems
And one fix to inode size handling:
- fix handling of preallocated extents beyond i_size when not using
[9 lines not shown]
Merge tag 'xfs-fixes-7.1-rc5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull xfs fix from Carlos Maiolino:
"A single fix for a race in xfs buffer cache which may lead to
filesystem shutdown due to inconsistent metadata if the buffer
lookup happens to find an old dead buffer still in the cache"
* tag 'xfs-fixes-7.1-rc5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
xfs: fix a buffer lookup against removal race
www/opengist: Update to 1.12.2
Changes since 1.12.1:
v1.12.2
Added
* Search all fields (#622).
* Display a form to create an Opengist account coming from a OAuth
provider (#623).
* Rebuild search index in admin options (#647).
Fixed
* Clean file path names on file creation (#624).
* Support UTF-8 on gist download (#625).
* CSRF skipper only for GET *.js request (#627).
* Async-loaded gist embed scripts (#630).
[7 lines not shown]
callout(9): Clarify previous language about clarity/efficiency.
And with that, I think I'm done touching up callout(9) for now.
PR kern/60288: callout(9) does not document callout_schedule()
[offload] Fix --libomptarget-nvptx-bc-path in tests
PR #198622, which landed as 3383f0d6fe01, causes 272 `libomptarget ::
nvptx64-nvidia-cuda` test fails on my system with:
```
clang: error: bitcode library '/home/jdenny/llvm/build/\./lib/x86_64-unknown-linux-gnu/nvptx64-nvidia-cuda' does not exist
```
This patch fixes that.
NAS-141131 / 27.0.0-BETA.1 / Set PARALLEL_SHUTDOWN for faster guest shutdown (#18989)
## Problem
On shutdown/reboot, TrueNAS stops containers and VMs one at a time,
waiting up to the per-guest shutdown timeout (90s by default) for each.
With many guests, this serializes into a long wait — a system with 10
containers and 10 VMs can spend most of its shutdown idle, waiting on
guests one after another.
## Solution
Set `PARALLEL_SHUTDOWN` in `/etc/default/libvirt-guests` so all
containers shut down concurrently and all VMs shut down concurrently.
The per-guest timeout is unchanged; the waits just happen in parallel.
libvirt applies `PARALLEL_SHUTDOWN` independently per URI (lxc, qemu),
so the cap only needs to cover the larger batch — hence
`max(len(containers), len(vms), 1)`.
[RISCV] Reserve all sub-registers of user reserved GPRs (#199302)
When a GPR is reserved by the user (e.g., via `-mattr=+reserve-x27`)
or marked as constant, only the top-level register was being marked
reserved in `RISCVRegisterInfo::getReservedRegs`. Its sub-registers
(`X27_W` and `X27_H`) remained unreserved.
This broke `LiveIntervals` when register pressure tracking was enabled
by #115445. Because the sub-registers were not reserved, the register
unit was considered non-reserved, causing `LiveIntervals` to track its
liveness and crash in the Machine Verifier due to the reserved
register missing from basic block live-in lists.
Instead, we should ensure that reserving a register also reserves all
of its sub-registers, so that the register unit is correctly
identified as reserved and ignored by `LiveIntervals`.
Fixes #176227
callout(9): Prefer callout_setfunc/schedule more explicitly.
It is better on clarity grounds; the efficiency difference is really
quite minor.
Prompted by:
PR kern/60288: callout(9) does not document callout_schedule()
callout(9): Partially fix markup error in previous.
Tried to spell out that it will call func(arg) and forgot to fix it
before previous commit. Doesn't look right now but at least it is
not as thoroughly wrong as something that renders as Fa(func, arg).
(This is an invitation for our resident mdoc wizards to correct my
infelicities!)
PR kern/60288: callout(9) does not document callout_schedule()
callout(9): Clarify callout_schedule, _setfunc, and _reset.
Might be better to use .Bl -tag instead of paragraphs of prose too.
PR kern/60288: callout(9) does not document callout_schedule()
