security/vuxml: Document terraform exclusion bypass
go-slug before v0.18.3, bundled in terraform, does not consistently
match .terraformignore rules against canonically equivalent Unicode
filenames, so files meant to be excluded can end up in uploads to
HCP Terraform or Terraform Enterprise. Fixed in terraform 1.15.9.
Security: CVE-2026-14978
Sponsored by: Netzkommune GmbH
sysutils/terraform: Update to 1.15.9, fix LICENSE
Update from 1.15.3 to 1.15.9. 1.15.9 updates go-slug to v0.18.3,
addressing CVE-2026-14978, an exclusion bypass in .terraformignore
handling. The version proposed in the PR, 1.15.8, still carries the
affected go-slug v0.18.1, hence the jump to 1.15.9.
The remaining changes are bugfixes: crashes in init and console,
wrong exit codes for variable errors in plan, query and refresh,
child module and submodule validation, several module installation
edge cases, and concurrency safety in the config parsers.
PR: 297296
Security: CVE-2026-14978
Approved by: maintainer timeout (dutra)
Sponsored by: Netzkommune GmbH
[libc++] Give the LNT tooling its own requirements.txt (#217889)
The LNT tooling alone has way fewer dependencies. Using a smaller
requirements.txt should speed up the "request historical benchmark data"
cron job that runs every 30 minutes and needs to install them.
libkern.h: remove HAVE_INLINE_* macros
The final consumer of this was OpenZFS, fixed in ffaea0831973 (thanks
mav@). That change has been present in all active OpenZFS release
branches for at least 6 months. These can finally be retired.
Reviewed by: mav
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D55201
dmu_redact_snap: Do proper cleanup on ENAMETOOLONG
If the redaction bookmark name exceeds ZFS_MAX_DATASET_NAME_LEN, we
leak the dataset hold, long hold, and decrypt key mapping on the target
snapshot, plus the same three references on each origin snapshot in
args[].
The leaked long holds leave those datasets busy such that destroy,
unmount, and zfs send will return EBUSY and the key mappings never drop.
Using goto out like the other error paths avoids this.
Reported-by: Grok 4.6 Build Beta
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Signed-off-by: Richard Yao <richard at ryao.dev>
Closes #18962
jh7110_gpio: driver enhancements
Fix reporting of state and capabilities by the gpioctl command.
Support selection of pull-up and pull-down resistors.
Support second gpio device (AON - always on power domain) to allow
attaching gpioled device to visionfive2 status LED or querying boot
selection switches.
Reviewed by: mhorne
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D58693
jh7110_gpio: remove unneeded cleanup
Any failure within bus_alloc_resources() will call bus_release_resources();
thus the call is redundant here.
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
dmu_recv_begin_check: dsl_dataset_rele() should be called on ds
We call dsl_dataset_hold() to initialize ds, and are supposed to call
dsl_dataset_rele() on ds when we are done. In two error paths, we call
dsl_dataset_rele_flags(). If ds is an encrypted dataset, this can drop
the key mapping for the dataset, which will cause run time issues. On
unencrypted datasets, this is a no-op.
Reported-by: Grok 4.6 Build Beta
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Signed-off-by: Richard Yao <richard at ryao.dev>
Closes #18961
[bazel][mlir] Fix lit.site.cfg substitution for MLIR_RUN_ARM_NEON_TESTS (#217973)
Follow-up to ee0f7ff7e697 which renamed MLIR_RUN_ARM_I8MM_TESTS to
MLIR_RUN_ARM_NEON_TESTS in lit.site.cfg.py.in.
Merge tag 'fbdev-for-7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev
Pull fbdev updates from Helge Deller:
"The usual bunch of many small fixes in various fbdev drivers, but
more interestingly the Vodoo3/4/5 cards will now be initialized even
without PC BIOS support and vintage Atari computers gain more color
depths and console acceleration on SuperVidel's SuperBlitter chips.
New features:
- Allow Vodoo3/4/5 card to be initialized without PC-BIOS (Daniel
Palmer)
- Add support for SuperVidel's SuperBlitter (Miro Kropacek)
- Add further video bit depths (Miro Kropacek)
- Detect default graphics card for console output on sticon/parisc
(Helge Deller)
Fixes:
- kyro: Validate overlay viewport coordinates (Danila Chernetsov)
- platinumfb: add error checking for ioremap calls (BingKun Yue)
[48 lines not shown]
[clang] Move the diagnostic of unexpected token after module name from phase 4 to phase 7 (#187846)
The PR https://github.com/llvm/llvm-project/pull/107168 implement
[CWG2947](https://cplusplus.github.io/CWG/issues/2947.html). And clang
checks next pp-token after module name in phase 4.
This PR move the check to phase 7, there are three main motivations:
1. We already convert the module name pp-tokens sequence into a
annot_module_name token, so for the following case, macro expansion will
be disabled.
2. In the original implementation, we need to look ahead a token even if
we already hit an `eod` token, but in phase7, we don't need to look
ahead a token.
3. The original implementation checked and emit a diagnosis in phase 4,
and then skipped these unexpected tokens in phase 7. Now we've merged
them into one step and are able to get a diagnosis approximate as
before.
```cpp
[18 lines not shown]
Revert "[mlir][IR] Add SymbolUserTypeInterface (#198435)" (#217959)
Looking forward to this feature, but the verification cost presently is
much too high: 2-3x+ end-to-end for CIRCT production workloads, as well
as a noticeable bump to MaxRSS. A user has reported their workload is
now 1.85x (#212160).
This verifier performance hit impacts all MLIR projects using the common
SymbolTable regardless of whether they make use of this interface.
Presently there are no in-tree users.
Promising work to reduce this cost (#212160, #212354) is underway, but
neither are ready yet.
Since the entire purpose of this interface is to support this
verification, revert this entirely for now while the performance story
is worked out.
This reverts commit 8c2d7cc3a9983459628c028d8537eaf79551f396.
[lldb][test] Fix 64-bit register assumption in wrapped frame test (#217659)
Added in #216840 / b0e9c530b5f0206de4a4f59f6728dbd5f10a5ca2.
This is failing on our downstream Arm 32-bit Linux bot:
```
* thread #1, name = 'a.out', stop reason = breakpoint 1.1
* frame #0: 0x013d0630 a.out`compute(a=<unavailable>, b=<unavailable>) at main.c:3:10 [synthetic]
frame #1: 0x013d065c a.out`main at main.c:6:25
frame #2: 0xea2b739a libc.so.6`
frame #3: 0xea2b743e libc.so.6`__libc_start_main + 94
frame #4: 0x013d0538 a.out`_start + 40
Expecting sub string: "compute(a=3, b=4)" (was not found)
```
I have not had time to reproduce it locally, but I did notice that the
test packs a struct of registers using `Q` (8 bytes) regardless of
register size.
[6 lines not shown]
Linux: allow more time for snapshot automount teardown
Snapshot destruction can race with the delayed dput()/mntput() work
triggered after accessing a snapshot through .zfs/snapshot. If that
work takes longer than 20 milliseconds, the snapshot remains long-held
and zfs destroy returns EBUSY, which for example causes ZTS tests to
fail spuriously.
Relax the unmount deadline from 20 to max 40 milliseconds. The wait
continues to exit earlier than that if the teardown completes earlier.
This fixes spurious ZTS failures such as snapshot/snapshot_00
{1,2,3,5,6,7,8,12}_pos and snapshot/rollback_002_pos especially with
--enable-debug builds since e8e3076927039bc6a2094c43e3ac4e255884177f
Reviewed-by: George Melikov <mail at gmelikov.ru>
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Rob Norris <rob.norris at klarasystems.com>
Signed-off-by: Wolfgang Hoschek <wolfgang.hoschek at mac.com>
Closes #18965
[DWARFLinker] Fix getContaingFile typo (NFC) (#217957)
Rename CompileUnit::getContaingFile to getContainingFile and update its
call sites in the parallel DWARF linker.
[CIR] Allow only CIR types in function signatures (#215922)
The calling convention lowering pass expects cir.func operations to
contain only CIR types in the signature. This change adds verifier
support to enforce that.
In the process, I discovered that it wasn't possible to walk the
subtypes of a CIR struct or union. The `AttrTypeSubElementHandler`
implementation to handle that (including the TODO comment) is copied
from the LLVM struct type handling.
Adding tests for this revealed a problem where if the `FuncType`
verifier reports an error, the `FuncOp` parser asserted. This change
fixes that by using `FuncType::getChecked()` to catch and report the
error.
[LLVMABI][AARCH64] Support transparent union arguments (#217686)
This adds support for using the first field in a transparent union for
the purposes of argument classification.
The `useFirstFieldIfTransparentUnion` function was already implemented
for the `X86_64TargetInfo` class. I moved it to the `TargetInfo` base
class because there is nothing target-specific about it.
Assisted-by: Cursor / various models
[llvm-objcopy] Stream ELF output to regular files
Write ELF output directly to seekable regular files instead of first allocating a buffer for the entire output. Keep buffered output for stdout and other non-seekable streams.
Use separate buffered and file-backed output implementations. Serialize regenerated metadata sequentially, seeking once per output range, and report sticky file errors after writing finishes. Truncate and extend seekable output up front so unwritten layout gaps read as zero without being materialized; explicitly overwrite only removed section contents within copied segments.
On a synthetic stamping-style ELF containing a 1 GiB payload, three warm-cache no-op copies had median peak RSS of 2,102,916 KiB before and 1,053,844 KiB after (49.9% lower). Median wall time improved from 1.06 s to 0.77 s, and the outputs were byte-identical.
Co-authored-by: Jeremy Braun <jtbraun at meta.com>
Assisted-by: OpenAI Codex
[Support] Support seekable temporary output streams
Use raw_fd_stream for temporary outputs so callbacks can perform positioned writes and resize the destination. Add raw_fd_ostream::takeError and raw_fd_stream::resize, and return stream failures through Error while preserving an existing destination.
Co-authored-by: Jeremy Braun <jtbraun at meta.com>
Assisted-by: OpenAI Codex
[llvm-objcopy] Route section copies through writeSectionContents
Centralize section byte copies behind a virtual helper so ELF output can later target either a memory buffer or a seekable stream. Materialize SHT_SYMTAB_SHNDX entries using the target ELF word type to preserve output endianness.
Co-authored-by: Jeremy Braun <jtbraun at meta.com>
Assisted-by: OpenAI Codex
[lldb] fix arm64e tests not compiling with an arm64e target (#216397)
Arm64eTestBase.build() only overrode TRIPLE, but ARCH_CFLAGS is a Make
command-line variable set separately by the test harness to a non-arm64e
flag. A plain in-Makefile assignment can't override a command-line
variable, so the compiler silently fell back to the host's default
(non-arm64e) triple and __ptrauth attributes failed to compile. Now
overrides ARCH_CFLAGS too.
