LinuxKPI: 802.11: assert wiphy lock for lkpi_bss_info_change() and MO
Finish reviewing all callers for lkpi_80211_mo_link_info_changed() and
lkpi_80211_mo_bss_info_changed(), which are called from
lkpi_bss_info_change() only. Add the lockdep_assert_wiphy() to
lkpi_bss_info_change() and make sure all callers are holding the
wiphy lock.
PR: 297228
Sponsored by: The FreeBSD Foundation
MFC after: 3 days
[WebAssembly] Avoid same-block dominance walks in RegStackify (NFCI) (#218369)
RegStackify asks whether one use dominates the others.
But when both uses are in the same block, MachineDominatorTree answers
that by walking the block from the start.
Use the SlotIndexes already available here instead.
This avoids repeatedly walking over DBG_VALUEs and other instructions in
large blocks.
(cherry picked from commit fad811bffe33b7858a46ccb76259e989d780b6b0)
workflows/release-binaries.yml: Only dump the wix logs on failure (#218810)
There is currently a bug in the path on ARM64 Windows, so this step
always fails. Running it after a successful build doesn't make much
sense anyway since since we don't need to see the logs for a good build.
Also, we risk having it fail the whole job even after a successful build
(like what is currently happening on ARM64 Windows), so that's another
reason only to run this when the bulid fails.
(cherry picked from commit c3badbb25e225b8ea428c65b7729c7f64efdd245)
[AArch64] Use SDValue to pass to vectorToScalarBitmask. (#218717)
Passing a SDNode loses whether the value is result 1 from a
uadd_with_overflow. Pass the SDValue instead.
Fixes #218668
(cherry picked from commit 14bbf16732524a83ca0b83686988db799dabb974)
If the address of the isa_pointer is returned as an error don't ask if it is a tagged pointer (#213163)
The answer isn't right and the wrong type might stick and cause
downstream failures.
Note, the correct solution to this is to distinguish between "couldn't
get the address" and "got a real value of LLDB_INVALID_ADDRESS" but
piping an optional all the way down and then through all the uses is an
intrusive change which I don't have time for right now. That only risk
is that this really IS a tagged pointer with the value
LLDB_INVALID_ADDRESS, so this seems an acceptable workaround.
I ran across this when debugging the ObjC test failures in the ObjC
testuite after 8b9cce358bef26ae4cb9275dd6a43f903bafbaa0. This patch
clears up all those testsuite failures, which should stand as a test for
this patch when I resubmit that change.
(cherry picked from commit 8fbdc8cd027176fb54c5fbcd7688fe78eed0154f)
Use static_pointer_cast to do SyntheticChildrenSP -> ScriptedSyntheticChildrenSP (#216181)
FormatManager::GetSyntheticForType was taking a pointer out one shared
pointer and making a new shared pointer referring to it which messes up
the lifecycle of the object.
This is just a little thinko from the original implementation. We do the
same thing in several other places in the TypeCategory, etc. and it's
done correctly in all the other places.
I'm not adding a test here because trying to guess what you have to do
to cause one or the other shared_pointer to get their reference count to
0 isn't particularly stable.
The testing for SBTypeSynthetic is pretty minimal - it would be better
to write a complete test for this class, which would have tripped this.
But that's a bigger task, and I want to get this obvious crasher fix in
now.
[5 lines not shown]
resterm: Update to 1.4.0
New
Polling and retries
Improved behavior
The TUI shows progress while a request is polling or retrying.
Request assertions, captures, and response test scripts run only after the final response.
Repeated attempts appear as one logical history entry.
Reported duration includes attempts and time spent waiting.
Request bodies are buffered and replayed safely between attempts.
Dynamic request values, such as generated UUIDs and timestamps, remain stable across attempts.
Retry exhaustion and polling timeouts produce clear errors.
Invalid Retry-After headers are ignored with a warning instead of failing the request.
tree-sitter: updated to 0.26.13
0.26.13
fix(query): correctly identify MISSING nodes in queries
fix(query): correctly set a state's skipped_quantifier flag when a
fix(generate): fold case-insensitive patterns at the AST leaves
fix(parser): avoid wide error nodes on unparseable input
fix(ci): run all workspace tests
build(deps): bump wasmtime-c-api to v36.0.14
fix(rust): remove must_use attribute from Tree::changed_ranges
dnscontrol: Update to 5.0.0
Changes
The list is too long to include all commits, but here are the highlights:
Add factory for models.DomainConfig: models.NewDomainConfig(zone).
Add factories for models.RecordConfig, replace old code where we can.
Down-casing, canonicalization, IDN conversion, stutter checking, and normalizing fields is now done when making the RecordConfig, not at the validation/normalization step later in the pipeline. As a result, errors are reported sooner and more accurately. pkg/normalize/validate.go still exists and is used, but is slowly being deprecated.
Remove the rtypecontrol module. In the few places it was used, replace with the new RDATA functionality.
DNS types RP and DS were reimplemented using the new RDATA system.
Replace RecordConfig.Comparable with RecordConfig.ComparableV3 (name change to find stragglers).
Custom types are now described in YAML with code generated automatically (pkg/privatetypes/types_generate.yaml)
TLSA comparison is now done on ToUpper, not ToLower, strings.
Added a "cookbook" of how to use new factories: Cookbook.
Integration tests: Test cfworkers and cfredirect by default.
Integration tests: Improve SVCB/HTTPS tests, especially for ech=IGNORE
LOC() is now a "builder" that outputs LOC records.
LOC floating point rounding error fixed
Builders are registered using models.RegisterBuilder()
[13 lines not shown]
[analyzer] Fix assertion in BitwiseShiftChecker from getExtValue (#218940)
`APSInt::getExtValue()` asserts `isRepresentableByInt64()`, which for an
unsigned value means it must fit in 63 bits. `checkOvershift()` called
it unguarded on a solver-derived lower bound, so any bound at or above
2^63 crashed with:
`Assertion 'isRepresentableByInt64() && "Too many bits for int64_t"'
failed.`
```c++
unsigned huge_right_operand_symbolic(unsigned x, unsigned long long t) {
if (t < 18000000000000000000ULL)
return 0;
return x >> t; // no-crash: gh #218867
}
```
Format the `APSInt` directly instead. Its stream operator honors the
value's own signedness, so bounds of any width print correctly, matching
[24 lines not shown]
security/py-biscuit-auth: Convert build to use PEP 517 and rename to PyPI name
* Rename port to PyPI name according to Python policy
* Move build completely to PEP 517
* Bump consumers: www/bunkerweb/Makefile
* Simplify Python discovery; the build frontend will pass the interpreter
New name: security/py-biscuit-python
Co-authored-by: Jochen Neumeister <joneum at FreeBSD.org>
PR: 297823
Approved by: joneum (maintainer)
Differential Revision: https://reviews.freebsd.org/D59133
[gold] Use ld.bfd for tests (#130981)
The gold linker is deprecated and no longer part of the default binutils
source distribution. LLVM's gold plugin, despite its name, does not
actually require the gold linker, it is compatible with any linker
implementing the necessary plugin interface, including the normal ld.bfd
linker. However, our tests for the gold plugin currently require the
gold linker.
This PR switches the tests to the ld.bfd instead, to the degree that
this is possible. A number of tests keep using gold, because they use
flags that ld.bfd only supports in very recent versions
(`--section-ordering-file` since 2.43 and `--start-lib` since 2.47).
The `thinlto.ll` test is changed to use `test -s` instead of `test -e`,
because ld.bfd will always create the (empty) output file, even if
`--plugin-opt=thinlto-index-only` is specified.
The `linkonce_odr_unnamed_addr.ll` test adds some uses of the
[9 lines not shown]
[RISCV] Support version 0.9 of Zvabd (#218576)
This commit includes support for the ARC approved version of Zvabd
(https://github.com/riscv/riscv-isa-manual/pull/3279), including code
generation support and intrinsic support. Intrinsic doc:
https://github.com/riscv-non-isa/riscv-rvv-intrinsic-doc/pull/436.
In addition, the constraint `DestEEW = EEWSEWx2` is now used for
widening vwabda[u] instructions for correct metadata.
Co-authored-by: renndong <liumingliang.dev at bytedance.com>
Co-authored-by: Pengcheng Wang <wangpengcheng.pp at bytedance.com>
Assisted-by: AI
rsa_eay: Replace handrolled BN_bn2binpad with the real thing
Just a tiny little bit of lipstick on this entelodont. This is simpler
and does not change behavior as BN_bn2binpad() returns -1 on failure and
num on success.
jsing points out that BN_bn2binpad() is constant time.
ok jsing kenjiro
PS: henning, you owe me a significant amount of quality beverages for
making me look at this particular tire fire (and corresponding XS files).
[LLD][COFF] Set the Thumb bit on locally imported ARMNT function poin… (#215919)
When a dllimport reference turns out to be locally defined, lld synthesises the
__imp_ pointer itself in LocalImportChunk. On ARMNT it was written unadjusted, so
an indirect call through the slot requests ARM state on a Thumb-only target.
Adjust it as DelayAddressChunk and AddressTableChunk already do, excluding data:
dllimport of a locally defined variable is valid and its pointer must not change.
Assisted-by: Claude Opus 5 (Anthropic)
