Merge tag 'pci-v7.3-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci
Pull PCI fix from Bjorn Helgaas:
- Enable clock after core reset is asserted to fix enumeration
regression on i.MX6Q Apalis platforms with ASM1061/ASM1062 SATA
controllers (Richard Zhu)
* tag 'pci-v7.3-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci:
PCI: imx6: Move clock enable after core reset assertion
18413 zfs: spa_sync_upgrades() should only take lock when needed
Reviewed by: Bill Sommerfeld <sommerfeld at hamachi.org>
Reviewed by: C Fraire <cfraire at me.com>
Approved by: Gordon Ross <gordon.w.ross at gmail.com>
Exclude tailcallelim test (#224708)
keeping the bot green. This failure was introduced in PR #221694, but
tailcallelimination isn't yet clean wrt profcheck
Revert "virtual_oss(8): Fix cuse.ko check"
parse_options() was moved above cuse_init(), which makes every single
regular virtual_oss invocation which uses cuse_dev_create() fail.
This reverts commit f014795ec3bd5efb88dfc249599e9665dc10a59e.
[AMDGPU][MC] Upstream gfx11/gfx12 true16 assembler test coverage
Upstream new assembler test cases, covering true16 .l/.h operands and op_sel
handling that had no upstream coverage.
[CIR][NFC] Fix compilation error CIRGenModule (#224694)
Fix deduced conflicting types for parameter when calling std::max with
unsigned long and unsigned long long, can be fixed by
`std::max(f.getAlignment().value_or(1), 2ull)` but in this line, the
alignment is always less than 2 because of the parent if condition, so
max is always 2
[AMDGPU][MC] Upstream gfx11/gfx12 true16 assembler test coverage
Upstream new assembler test cases, covering true16 .l/.h operands and op_sel
handling that had no upstream coverage.
[AMDGPU][MC] Upstream gfx12 true16 disassembler test coverage
Upstream new gfx12 disassembler test cases, covering true16 operand (.l/.h)
and op_sel decoding for f16 opcodes that had no upstream coverage:
[lldb] Follow serial outlined functions when scanning for an unwind plan (#222800)
For code-size-constrained builds the compiler's instruction outliner
finds
identical instruction sequences across functions, moves them into a
single
OUTLINED_FUNCTION_<n>, and has every user call it. Instructions from a
function's prologue, body or epilogue may all be outlined.
lldb's instruction-emulation UnwindPlan creator scans the instructions
of a
function and, following the ABI's calling convention, assumes a call
leaves the
stack and registers in a known state. That assumption does not hold for
outlined functions: when prologue and epilogue instructions are outlined
out of
the function body, the UnwindPlan misses those register spills and
restores,
which leads to inaccurate variable tracking in the caller's frames.
[20 lines not shown]
[lldb] Don't consult the plan stack for a stop an auto-continue will discard (#215522)
Fixes part (2) of #215189. The sibling PR for part (1) is #215521. The
two are
independent, but are best landed together.
When a completed thread plan auto-continues, `Thread::ShouldStop()`
still
consults subsequent plans and then discards their stop decisions. Those
calls
can change the state of the plans being consulted. In the failing case,
`ThreadPlanRunToAddress` loses the breakpoint it was running to, so the
process
runs past the requested address.
This does not require a scripted plan:
```python
# thread stopped on an enabled breakpoint site
[46 lines not shown]
[lldb] Remove the unused Process::ReadMemoryInChunks (#224656)
`Process::ReadMemoryInChunks` and its `ReadMemoryChunkCallback` typedef
have no callers left in the tree, no unit tests, and no SB API exposure.
This commit removes it.
The method was added in commit f869d6efeec8 (#129307) for the minidump
writer, which was its only caller. Then, commit 7f04a40a220e (#212641)
replaced that call with a direct loop over `ReadMemoryFromInferior` in
`MinidumpFileBuilder::ReadWriteMemoryInChunks`, leaving this method
dead.
This commit also drop the reference to this method from the description
of
`TestProcessSaveCoreMinidumpSizeMismatch.py`. The test is unchanged.
18411 format: remove __STDC__
Reviewed by: Robert Mustacchi <rm at fingolfin.org>
Reviewed by: Andy Fiddaman <illumos at fiddaman.net>
Approved by: Gordon Ross <gordon.w.ross at gmail.com>
[AMDGPU][MC] Upstream gfx11 true16 disassembler test coverage
Upstream new gfx11 disassembler test cases, mostly covering true16 operand
(.l/.h) and op_sel decoding that had no upstream coverage.
RISCV: Don't use MCTargetOptions::ABIName in the ELF target streamer
The abi name should come from the target-abi module flag in codegen,
which should be set up in the AsmPrinter. The ABI name field should
only be of practical use in the assembler, which reads the flag in
onBeginOfFile.
Co-Authored-By: Claude <noreply at anthropic.com> (Claude Opus 4.8)
[GitHub] Avoid downloading outputs during Bazel tests when possible
I noticed recently that `Bazel Build/Test` takes 90s even when everything is cached. It looks like it's downloading a GiB of artifacts from the cache. For example, in [a recent run](https://github.com/llvm/llvm-project/actions/runs/35147456695/job/104967035656):
```
[82,641 / 90,341] 1094 / 7245 tests; Linking external/+_repo_rules+llvm-project/flang/lib/Semantics/libFortranSemantics.a; Downloading external/+_repo_rules+llvm-project/flang/lib/Semantics/libFortranSemantics.a, 260.4 MiB / 288.7 MiB; 1s remote-cache ... (62 actions, 10 running)
[88,426 / 91,191] 1238 / 7245 tests; Linking external/+_repo_rules+llvm-project/mlir/mlir-reduce; Downloading external/+_repo_rules+llvm-project/mlir/mlir-reduce, 337.0 MiB / 344.6 MiB; 13s remote-cache ... (58 actions, 0 running)
[88,870 / 92,185] 1315 / 7245 tests; Linking external/+_repo_rules+llvm-project/mlir/mlir-query; Downloading external/+_repo_rules+llvm-project/mlir/mlir-query, 241.9 MiB / 264.2 MiB; 11s remote-cache ... (55 actions, 0 running)
...
Executed 0 out of 7245 tests: 7245 tests pass.
```
Adding `--remote_download_outputs=minimal` makes it so Bazel only downloads artifacts if they are needed for local actions. This saves about ~30s on my machine (90s -> 60s). The next limiting factor is that Bazel has 100 max # of HTTP connections. If you bumped that up, the fully-cached case reduces to 20s total, but I don't think we should necessarily do that. It's just a little silly that Bazel spends about 40s just asking "is this cached?" over and over again.
www/angie-module-jwt: Update to 3.4.6
This bugfix release fixes the module's test suite:
test_conf forwarded an unquoted $@, so the expected message was split
on spaces and only its first word was ever grepped. Two expectations
were pointing at the wrong configuration file, unnoticed.
PR: 298635
Changes: https://github.com/max-lt/nginx-jwt-module/releases/tag/v3.4.6
Sponsored by: Netzkommune GmbH
www/angie-module-auth-jwt: Update to 0.15.0
This new release adds the nxe-phase submodule and bumps the version of
nxe-jwx from 0.2.0 to 0.4.0.
PR: 298634
Changes: https://github.com/kjdev/nginx-auth-jwt/releases
Sponsored by: Netzkommune GmbH
www/angie-module-njs: Security update to 1.0.1
This maintenance update of njs fixes three security issues:
- Access control bypass in js_access when an asynchronous request body
continuation threw an exception or produced an unhandled rejection
(CVE-2026-18329). Previously, nginx could continue processing the
request as though the js_access check had succeeded. Affects
0.9.9-1.0.0. Thanks to Ta Duc Thien.
- Worker process crash when reading Response.statusText after an
upstream server returned a status line with an empty reason phrase
(CVE-2026-78222). Affects 0.5.1-1.0.0.
- Heap buffer overflow while parsing namespace prefix lists passed to
xml.exclusiveC14n() (CVE-2026-78689). Affects 0.7.10-1.0.0. Thanks to
Vladimir, Vulnerability Research Tech Lead @ Cyera, evilgensec.
PR: 298637
[3 lines not shown]
www/angie: Security update to 1.12.2
This maintenance release fixes CVE-2026-90439:
When using an OpenSSL version without native HTTP/3 support (3.5.0
or earlier), if the default server for the address that accepted a
regular HTTPS request also used HTTP/3 (the listen directive with the
quic parameter, possibly on a different port), while a server block
without HTTP/3 was selected by domain name (SNI), limited worker process
memory corruption or a worker process crash could occur
(CVE-2026-90439); the fix was ported from nginx 1.31.6.
PR: 298632
Changes: https://en.angie.software/angie/docs/oss_changes/#angie-1-12-2
Security: 6cf2ff4b-b38c-11f1-a655-3497f65b111b
Sponsored by: Netzkommune GmbH
