workflows/release-tasks: Use app generated token for publishing lit releases (#195312)
We are trying to move a way from using secrets associated with the
llvmbot account, so this drops another one of its users.
[libc] Fix personality buildbot failures (#195364)
Remove the `#include <sys/personality.h>` from the implementation
header. On buildbots, the generated header does not exist at compile
time, so `-idirafter/usr/include` pulls in glibc's version instead.
Glibc's header uses `__BEGIN_DECLS` and `__THROW`, which are unavailable
in the freestanding build.
The include was unnecessary. The function signature only uses basic
types.
Fixes buildbot failures introduced by #195065:
- libc-aarch64-ubuntu-fullbuild-dbg
- libc-x86_64-debian-fullbuild-dbg-asan
- libc-x86_64-debian-fullbuild-dbg
- libc-x86_64-debian-gcc-fullbuild-dbg
[lldb] Thread DWARFExpression::Evaluate state through an EvalContext (NFCI) (#195220)
Collect the inputs, derived pointers, and mutable evaluation state of
DWARFExpression::Evaluate into a file-local EvalContext struct passed by
reference to the static helpers.
Two incidental fixes making this not-quite NFC:
1. Evaluate_DW_OP_deref_size renamed to Evaluate_DW_OP_deref and takes
the LocationAtom, so error messages name the actual opcode.
2. ResolveLoadAddress no longer crashes on null exe_ctx (uses
eval_ctx.target, which is null-safe).
I initially prototyped a visitor-like design, centered around a
DWARFEvaluator class with one method per opcode and shared state as
members. I discarded it because moving the simple operations out of the
switch hurt readability and increased mental overhead. Its only real
benefit were the cleaner signatures, which this patch achives by using
the new EvalContext.
workflows/release-tasks: Use app generated token for creating the release (#195219)
We are trying to move a way from using secrets associated with the
llvmbot account, so this drops another one of its users.
[lldb][debugserver] Don't duplicate loaded binaries in jStopInfo (#195343)
RNBRemote::GetJSONThreadsInfo() has a bool mode switch: Only
exception-related information information about threads which had an
exception, or full information about all threads. The exception-related
information is what ends up in the `jstopinfo` key in the stop packet,
asciihex encoded. The full information is what is sent for the
`jThreadsInfo` packet, with full information for all threads at a public
stop.
When I added the `added-binaries` and `detailed-binaries-info` keys to
the thread description, I incorrectly put this in the exception related
block of this method. Move that in to the "full information" section of
the method, so we don't duplicate the information that is included in
the stop packet, asciihex encoded at that.
rdar://176001611
[NFC][HLSL] Remove dead branch for const return by value (#194983)
Remove unreachable addConst() on the by-value return path of
addHandleAccessFunction.
No caller passes IsConstReturn=true with IsRef=false. The existing AST
tests ( StructuredBuffers-AST.hlsl, ByteAddressBuffers-AST.hlsl,
TypedBuffers-AST.hlsl) already assert the by-value Load return type is
non-const, so behavior is verified unchanged.
Assisted by: Github Copilot
Fixes https://github.com/llvm/llvm-project/issues/194982
powerpc: refactor dmamap setup; free dmamap in error paths
* refactor the dmamap allocation / setup path for future code changes
to align with arm64 busdma code;
* free the dmamap allocation if the dma segment list can't be allocated;
* free the dmamap allocation during the busdma dmamem allocation path
if the actual memory allocation itself fails.
Locally tested:
* POWER9 ppc64le native boot, Raptor Engineering Blackbird
* POWER8 ppc6le, IBM POWER S822LC
https://reviews.freebsd.org/D56244
powerpc: busdma declaration shuffling
Shuffle some of the declarations around to match other implementations.
Expected to be a no-op.
Differential Revision: https://reviews.freebsd.org/D56243
powerpc: use local flags for bounce buffers instead of common flags
Migrate to using local flags for bounce buffers instead of the
common flag field.
Differential Revision: https://reviews.freebsd.org/D56208
powerpc: add in some busdma domain setup
* Implement the basic tag domain set routine
* Set the domain to the parent domain if provided
This is just plumbing for eventual work to re-allocate things into
the currently configured domain.
Differential Revision: https://reviews.freebsd.org/D55315
powerpc: create a tag with the parents implementation if supplied
If a parent tag is supplied then use its implementation.
Differential Revision: https://reviews.freebsd.org/D55314
powerpc: initial straight port of busdma_machdep.c -> busdma_bounce.c
This is a straight port of the code and doesn't yet handle
different implementations (which will be in a subsequent commit.)
Locally tested:
* G5 SMP (2x PPC970mp)
* power8 / power9 pseries QEMU VM
* power8 powernv
Differential Revision: https://reviews.freebsd.org/D55313
net/libpfctl: add 15.1, remove 13.5
13.5 is end-of-life, remove it from this port.
Add 15.1, which is in the process of being released.
Deliberately do not bump PORTVERSION, because we don't change existing
libpfctl versions, we only add a new supported FreeBSD version.
PR: 294871
Sponsored by: Rubicon Communications, LLC ("Netgate")
Fix test's FileCheck match to allow a column number in message. (#195356)
In some cases, the cfi diagnostic is emitted with a column
number. Allow that in the test.
NAS-140840 / 27.0.0-BETA.1 / Clear rsync one-shot alerts on task delete (by creatorcary) (#18882)
### Summary
`RsyncFailed` / `RsyncSuccess` are `OneShotAlertClass` alerts with
`deleted_automatically = False` (`alert/source/rsync.py:5,23`), keyed on
the task id. They are created from `RsyncTaskService.run()` and cleared
at the top of the next run, but `RsyncTaskService.do_delete()` was not
clearing them. Deleting a task therefore left an orphaned critical alert
in the panel that the UI could no longer associate with any task —
dismissing it appeared to "stick" but on reload it was still there, and
the rsync task section on Data Protection no longer had the row it
referred to.
### Consistency with other task plugins
Plugins that use `OneShotAlertClass` for task alerts already do this
cleanup in their `do_delete`. Rsync was the outlier:
[19 lines not shown]
NAS-140840 / 26.0.0-RC.1 / Clear rsync one-shot alerts on task delete (#18880)
### Summary
`RsyncFailed` / `RsyncSuccess` are `OneShotAlertClass` alerts with
`deleted_automatically = False` (`alert/source/rsync.py:5,23`), keyed on
the task id. They are created from `RsyncTaskService.run()` and cleared
at the top of the next run, but `RsyncTaskService.do_delete()` was not
clearing them. Deleting a task therefore left an orphaned critical alert
in the panel that the UI could no longer associate with any task —
dismissing it appeared to "stick" but on reload it was still there, and
the rsync task section on Data Protection no longer had the row it
referred to.
### Consistency with other task plugins
Plugins that use `OneShotAlertClass` for task alerts already do this
cleanup in their `do_delete`. Rsync was the outlier:
[15 lines not shown]
PR/59957: Taylor R. Campbell: Centralize the disk open sequence from newfs
and tunefs to a new function "openspecial" and use it to fix this PR, and
the same issue with newfs_ext2fs.
[dsymutil] Make --linker explicit in every test (#195293)
Pass `--linker classic` or `--linker parallel` on every `dsymutil`
invocation instead of relying on the implicit default. This preserves
the existing coverage in preparation for toggling the default in the
future.
Tests previously exercising only one linker now mirror the RUN block for
the other, sharing FileCheck prefixes. Not all tests are compatible, and
I've added a FIXME to make them easy to spot.
clang: Stop using replace_extension when there's no extension (#195335)
The offload case is building a fresh filepath and there's no file
extension to replace. Just directly append the file extension to avoid
clobbering part of the path name if the triple contains a period.
Avoids confusing test updates in future triple patch.
namei: Preserve ABI root for absolute symlinks before fallback
D40479 changed namei() so that an absolute symlink target
encountered during an ABI-root lookup restarts from the native root.
This helps the native fallback case, but it also makes successful
lookups inside an ABI root escape that root while following absolute
symlinks.
Only switch absolute symlink lookup to the native root after namei()
is already in the restarted/native fallback pass.
Do not mark the lookup as restarted merely because an absolute
symlink was encountered while still resolving inside the ABI root.
This preserves the intended native fallback behavior while keeping
absolute symlinks within a successfully resolved ABI-root path in
the ABI namespace.
Signed-off-by: Ricardo Branco <rbranco at suse.de>
PR: 289739
[3 lines not shown]
Merge tag 'selinux-pr-20260501' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux
Pull selinux fixes from Paul Moore:
- Ensure SELinux is always properly accessing its own sock LSM state
- Only reserve an xattr slot for SELinux if it will be used
- Fix a SELinux auditing regression in the directory avdcache
* tag 'selinux-pr-20260501' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux:
selinux: fix avdcache auditing
selinux: don't reserve xattr slot when we won't fill it
selinux: use sk blob accessor in socket permission helpers
[flang][OpenMP] Support loop-associated metadirective variants (part 3)
Enable metadirective lowering for loop-associated variants such as
`do`, `simd`, `parallel do`, and `do simd`.
When a metadirective resolves to a loop-associated directive, the
sibling DO evaluation is spliced into the metadirective's evaluation
list so existing loop lowering finds it. Loop IV data-sharing
attributes are marked at lowering time since semantic analysis cannot
know which variant will be selected. The DataSharingProcessor is also
extended to handle spliced evaluations.
This patch is part of the feature work for #188820 and stacked on top
of #194424.
Assisted with copilot and GPT-5.4
futex: Drop CLONE_THREAD requirement for private default hash alloc
Currently need_futex_hash_allocate_default() depends on strict pthread
semantics, abusing CLONE_THREAD. This breaks the non-concurrency
assumptions when doing the mm->futex_ref pcpu allocations, leading to
bugs[0] when sharing the mm in other ways; ie:
BUG: KASAN: slab-use-after-free in futex_hash_put
... where the +1 bias can end up on a percpu counter that mm->futex_ref
no longer points at.
Loosen the check to cover any CLONE_VM clone, except vfork(). Excluding
vfork keeps the existing paths untouched (no overhead), and we can't
race in the first place: either the parent is suspended and the child
runs alone, or mm->futex_ref is already allocated from an earlier
CLONE_VM.
Link: https://lore.kernel.org/all/CAL_bE8LsmCQ-FAtYDuwbJhOkt9p2wwYQwAbMh=PifC=VsiBM6A@mail.gmail.com/ [0]
[4 lines not shown]
