[libc] Implement recvmmsg (on linux) (#202328)
The function (unlike sendmmsg) takes a timeout argument, so I make sure
to always call the version with a 64-bit time_t. I've also renamed the
sendmmsg_test.cpp unit test to sendrecvmmsg_test.cpp to test both
functions. I also updated the yaml config and docgen files to include
the new function and the struct_timespec type dependency.
Assisted by Gemini.
ipsec: disable scroll in authentication and children grids (#10407)
Since the grids live on a lower position on the screen, the height calculation may squash the entries. This should be solved by enforcing a minimum row constraint, but for ipsec specifically being able to see all children at all times is more important, which is what this commit aims to solve.
[Flang][OpenMP] Fix implicit symbol resolution for USE-renamed arrays (#189215)
[Flang][OpenMP] Fix USE-renamed array DSA in OpenMP regions
Problem: for a USE-renamed symbol (e.g. USE mod, ONLY: s_ary => ary),
the HostAssoc in the OMP scope was created under the original name
"ary" instead of the local alias "s_ary".
Fix: add a DeclareNewAccessEntity overload that takes an explicit
SourceName, and call it with symbol->name() (the alias) rather than
the ultimate symbol's name, so the HostAssoc is created under the
name the user wrote.
Fixes #185344
Assisted-by: Claude Sonnet 4.6
NAS-141260 / 26.0.0-RC.1 / Remove `use_attribute_docstrings=True` (by themylogin) (#19086)
`use_attribute_docstrings=True` increases models import time by 20-25%,
because it needs to re-parse all model python files to find the
docstrings. Takes too much time when legacy APIs are loaded at runtime.
Not worth it.
Original PR: https://github.com/truenas/middleware/pull/19068
---------
Co-authored-by: themylogin <themylogin at gmail.com>
[AMDGPU] remove DefIsPriv mapping (#202694)
Since various commits that now avoid immediately casting most
temporaries, and now follow Sema for variables, this looks like tests
pass now without needing a second map to correct those issues
afterwards. Hopefully this will help find any similar remaining issues
expeditiously, if any.
[clang] `this` getter missed in ConstructAttributeList (#203010)
In https://reviews.llvm.org/D159247 (400d3261a0da56554aee8e5a2fbc27eade9d05db)
it looks intended to update all of these calls, but missed this. The
effect is that a reference `&this` in a non-zero addrspace would take
this branch and crash there (because it ends up asserting that `this`
is a pointer). DRY the code since this branch looks like it kept
getting copied more incorrectly over time. I don't have an actual use
or test for this, I just noticed it while I was trying to break other
things in fuzzing.
[docs] try again to handle doxygen everywhere (#203081)
The previous attempt at this (b7da9565017e32c18b927a7637714d1b660b558d)
still broke standalone builds. Now I have locally tested standalone
flang, runtimes (with openmp), lldb, combined builds, and the utils
script. Hopefully that covers everything this time, and gets everything
into a more consistent state (always using the HandleDoxygen script in
the same way, included exactly once as required by the cmake design).
[LoopInterchange] Consolidate induction and reduction vars check (#203197)
Previously, the handling of PHI nodes in loop headers was scattered. In
particular, there were two separate functions, `findInductions` and
`findInductionAndReductions`, which made the code difficult to reason
about. This patch consolidates these two functions, along with their
related caller logic, into a single function,
`checkInductionsAndReductions`. Although some remarks and debug outputs
have changed as a result, I believe the functionality itself remains
unchanged.
py-daphne: updated to 4.2.2
4.2.2 (2026-06-03)
* Fixed a denial of service vulnerability via unbounded WebSocket message sizes.
Daphne previously passed no message or frame size limits to autobahn,
whose defaults are unbounded. This allowed an unauthenticated client
to exhaust server memory by sending a very large WebSocket
messages/frames (CVE-2026-44545).
Both limits now default to 1 MiB and can be configured via the new
``--websocket-max-message-size`` and ``--websocket-max-frame-size`` CLI
flags (or the matching ``Server`` constructor arguments). Pass ``0`` to
restore the previous unlimited behaviour.
Thanks to ParkHyunWoo for the report.
* Fixed a header injection vulnerability on the WebSocket upgrade path
(CVE-2026-44546).
[12 lines not shown]
ldns: updated to 1.9.2
1.9.2 2026-06-10
* Fix to set VERSION_INFO to create .so.3 instead of .so.11 which will
be reserved for a future 1.10.0 release
1.9.1 2026-06-10
* Bugfix: Insufficient verification that responses belong to a
query (CVE-2026-10846). Thanks Pablo Ruiz from 'codecome.ai'
net-im/py-zapzap: Update to 6.5.1.1
- Add a post-patch target to fix the distribution version, otherwise
the building process fails with the error:
===> Generating temporary packing list
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/local/lib/python3.11/site-packages/installer/__main__.py", line 115, in <module>
_main(sys.argv[1:], "python -m installer")
File "/usr/local/lib/python3.11/site-packages/installer/__main__.py", line 100, in _main
with WheelFile.open(wheel) as source:
File "/usr/local/lib/python3.11/contextlib.py", line 137, in __enter__
return next(self.gen)
^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/installer/sources.py", line 179, in open
with zipfile.ZipFile(path) as f:
^^^^^^^^^^^^^^^^^^^^^
[6 lines not shown]
[Dexter] Write expects for variables in Debugger scopes
Following on from the previous patch, this patch adds support for writing
expects from !value/all nodes, generating separate expects for each
variable in the requested debugger scope, for each continuous range of lines
it is live for.
[LoopInterchange] Bail out when outer loop latch PHI has non-PHI user (#201923)
When there are non-PHI instructions in the outer loop that use values
originating from the LCSSA PHIs of the inner loop, it becomes difficult
to adjust the wiring during the transformation. In fact, multiple issues
(#200819 and #201571) have been raised related to this pattern. #201059
tried to resolve the issue by modifying the transformation phase, but it
was insufficient.
Instead of spending effort in the transformation phase, this patch adds
an additional check in the legality check and rejects such cases. I
think the cases rejected by this additional check are not very
practical, so the impact on realistic cases should be low, and it is
simpler than adjusting the wiring in the transformation phase.
This patch also effectively reverts #201059, as it is no longer
necessary.
Fix #201571.
[X86] Don't assert on EFLAGS copies in unreachable blocks (#203208)
X86FlagsCopyLowering collects the EFLAGS copies to lower using a
ReversePostOrderTraversal, which only visits blocks reachable from the
entry. Its end-of-pass verification, however, iterated over every block
in the function, so an EFLAGS copy left in an unreachable block (e.g.
produced by ISel for an always-taken branch whose other edge is dead)
tripped the "Unlowered EFLAGS copy!" assertion.
Such copies are harmless: the unreachable block is removed by the
unreachable-block elimination pass that runs right after this one,
before register allocation, so the copy never reaches a pass that cannot
handle it. Restrict the verification to reachable blocks (depth_first
from the entry) to match the set of blocks actually processed.
Found via fuzzing (llvm-isel-fuzzer).
Remove stale ARC graph names from reporting API
`reporting.get_data` accepted three graph names — `arcrate`, `arcactualrate`, `arcresult` — whose backing plugin classes were deleted during the ZFS netdata plugin rewrite. The Pydantic `Literal` and the in-memory `__graphs` dict drifted out of sync, so passing any of them crashed `netdata_get_data` with an uncaught `KeyError`.
Removed the dead names from `GraphIdentifier.name`'s `Literal` and docstring in both `v26_0_0/reporting.py` and `v27_0_0/reporting.py`. Added a `ReportingNetdataGetDataArgs.from_previous` on each so legacy WS clients walking the adapter chain get the dead entries silently filtered instead of a hard rejection at the final v27 boundary. Hardened the dispatch site in `plugins/reporting/graphs.py` to raise `CallError(ENOENT)` for any unknown name — mirroring what `netdata_graph` already does — so future schema/implementation drift surfaces as a clean RPC error rather than an unhandled exception.
