jail(3): fix common usage after mac.label support
Nobody else's mac.conf(5) has any entries for jails, so they get a
trivial ENOENT and we fail before we can fetch any jail parameters.
Most notably, this breaks `jls -s` / `jls -n` if you do not have any
loaded policy that applies jail labels.
Add an entry that works for everyone, and hardcode that as an ENOENT
fallback in libjail to provide a smoother transition. This is probably
not harmful to leave in long-term, since mac.conf(5) will override it.
This unearthed one additional issue, in that mac_get_prison() in the
MAC framework handled the no-label-policies bit wrong. We don't want
to break jail utilities enumerating jail parameters automatically, so
we must ingest the label in all cases -- we can still use it as a small
optimization to avoid trying to copy out any label. We will break
things if a non-optional element is specified in the copied in label,
but that's expected.
[8 lines not shown]
mac(4): also list jails in the example enumeration of objects
The prison may also be considered part of the subject by way of its
ucred association, but I don't think this is significantly different
enough today than before recent work -- policies could have always
taken them into account, and some did (e.g., mac_bsdextended).
Reported by: olce
Reviewed by: olce, ziaee
Differential Revision: https://reviews.freebsd.org/D54748
[Clang] Check enable_if attribute without delayed diagnostics (#176080)
We ensure immediate access control checking when evaluating the
enable_if attribute to rule out inaccessible constructors during
potential overload resolution, treating them as SFINAE errors rather
than hard errors, making the behavior more preferable with the nature of
the enable_if attribute.
Compared to the last patch, we now avoid switching the DC directly
because there are cases where we're checking enable_if attribute within
a lambda and getCurLambda() requires a lambda context to distinguish
from template instantiation.
This reapplies #175899
Fixes https://github.com/llvm/llvm-project/issues/175895
[Clang] Ensure a lambda DeclContext in BuildLambdaExpr (#176319)
Since 5f9630b388, we only remove the LSI after the evaluation context is
popped. The TreeTransform of immediate functions may call getCurLambda,
which requires both the paired LSI and the lambda DeclContext. In
TransformLambdaExpr, we already switched the context, but this is not
the case when parsing a lambda expression.
No release note, as this is a regression from 22.
Fixes https://github.com/llvm/llvm-project/issues/176045
Add clustered share_info.tdb handling
This commit ensures our utilities to manipulate samba's share_info.tdb
file are suitably agnostic as to whether the database is clustered.
math/octave-forge-instrument-control: New port.
Octave low level I/O functions for serial, i2c, parallel, tcp, gpib,
udp and usbtmc interfaces. Not vxi11 as there doesn't seem to be
FreeBSD support.
workflows/release-lit: Update workflow and enable trusted publishing with pypi (#174907)
This makes some small improvements to the workflow including using some
more modern python packaging modules and also enables the trusted
publishing for pypi. This will allow us to publish lit packages to pypi
without needing to use an access token.
This action also now uses the pypi environment which will only publish
files when triggered by an llvm-* tag.
Update to use jdk-11:
* Set the jdk version to 11 only and adjust startup scripts so that
java does not need to be in the path to run.
* Skip tests using jaxb which was removed in jdk11
ok tb@
[NFCI][AMDGPU] Use X-macro to reduce boilerplate in `GCNSubtarget.h`
`GCNSubtarget.h` contained a large amount of repetitive code following the pattern `bool HasXXX = false;` for member declarations and `bool hasXXX() const { return HasXXX; }` for getters. This boilerplate made the file unnecessarily long and harder to maintain.
This patch introduces an X-macro pattern `GCN_SUBTARGET_HAS_FEATURE` that consolidates 129 simple subtarget features into a single list. The macro is expanded twice: once in the protected section to generate member variable declarations, and once in the public section to generate the corresponding getter methods. This reduces the file by approximately 265 lines while preserving the exact same API and functionality. Features with complex getter logic or inconsistent naming conventions are left as manual implementations for future improvement.
Ideally, these could be generated by TableGen using `GET_SUBTARGETINFO_MACRO`, similar to the X86 backend. However, `AMDGPU.td` has several issues that prevent direct adoption: duplicate field names (e.g., `DumpCode` is set by both `FeatureDumpCode` and `FeatureDumpCodeLower`), and inconsistent naming conventions where many features don't have the `Has` prefix (e.g., `FlatAddressSpace`, `GFX10Insts`, `FP64`). Fixing these issues would require renaming fields in `AMDGPU.td` and updating all references, which is left for future work.
editors/openoffice-devel: Fix with python >= 3.12
Fix build with python >= 3.12.
Since this is only a build fix, and builds with older python versions
are not changed other than an additional BUILD_DEPENDS, no PORTREVISION
bump is necessary.
PR: 292190
Reported by: George Mitchell <george at m5p.com>
[mlir][scf] Skip ops having results with warning in forall-to-for pass (#175926)
Avoid converting scf.forall ops that have results in forall-to-for pass.
Emit a warning instead of failing the pass, so mlir-opt can still
produce output on mixed IR.
Fixes https://github.com/llvm/llvm-project/issues/174319
[LifetimeSafety] Detect dangling references to field members (#176805)
Add support for detecting dangling references to struct fields in the CFG-based lifetime analysis.
The tests now include cases where accessing fields of temporary objects leads to dangling references, which are properly detected.
- Added `VisitMemberExpr` method to the `FactsGenerator` class to handle field member expressions
- Implemented the method to create origin flow facts for field member expressions
- Updated tests to include CFG-based warnings for dangling references to struct fields
- Fixed previously disabled tests that can now detect these issues
Fixes https://github.com/llvm/llvm-project/issues/176144
NAS-139371 / 26.04 / Add support for clustered local SMB accounts (#18057)
This commit adds support for managing clustered accounts database for
SMB users and groups. This is accomplished by wrapping around existing
TDBHandle utils and expanding their functionality so that they also work
with clustered databases. The passdb-related functions now take a
clustered keyword argument, and group-mapping now has alternative
CLUSTERED path. On config change for `stateful_failover` we re-run the
`smb.configure` endpoint to ensure
that accounts are properly inserted into running configuration.
