libarchive: updated to 3.8.6
Libarchive 3.8.6 is a security and bugfix release.
Notable fixes:
libarchive: fix incompatibility with Nettle 4.x
libarchive: fix NULL pointer dereference in archive_acl_from_text_w()
bsdunzip: fix ISO week year and Gregorian year confusion
7zip: ix SEGV in check_7zip_header_in_sfx via ELF offset validation
7zip: fix out-of-bounds access on ELF 64-bit header
RAR5 reader: fix infinite loop in rar5 decompression
RAR5 reader: fix potential memory leak
RAR5: fix SIGSEGV when archive_read_support_format_rar5 is called twice
CAB reader: fix memory leak on repeated calls to archive_read_support_format_cab
mtree reader: Fix file descriptor leak in mtree parser cleanup
various small bugfixes in code and documentation
[mlir][func] Fix crashes in FuncToLLVM discardable attributes propagation logic (#188232)
Refactor how `func.func` discardable attributes are handled in the
Func-to-LLVM conversion. Instead of ad hoc checks for linkage and
readnone followed by a simple filter, the pass now generically processes
inherent attributes from LLVMFuncOp.
Attributes that correspond to inherent `llvm.func` ODS names can be
attached as `llvm.<name>` on `func.func` and are stripped to `<name>`
when building `LLVM::LLVMFuncOp`, so LLVM-specific knobs stay namespaced
on the source op but land on the right inherent slots on `llvm.func`.
Other discardable attributes continue to be propagated as-is.
Fixes #175959
Fixes #181464
Assisted-by: CLion code completion, GPT 5.3-Codex
[2 lines not shown]
[SLP] Fix incorrect operand info for select in getCmpSelInstrCost (#188506)
The operand info passed to getCmpSelInstrCost for Select instructions
was using operands 0 and 1 (condition and true value), but the API
expects info about the data operands (true and false values). For
selects, the data operands are at indices 1 and 2, not 0 and 1.
This led to the cost model receiving the condition's operand info
instead of the false arm's, potentially producing inaccurate cost
estimates.
[SLP] Fix incorrect operand info for select in getCmpSelInstrCost
The operand info passed to getCmpSelInstrCost for Select instructions
was using operands 0 and 1 (condition and true value), but the API
expects info about the data operands (true and false values). For
selects, the data operands are at indices 1 and 2, not 0 and 1.
This led to the cost model receiving the condition's operand info
instead of the false arm's, potentially producing inaccurate cost
estimates.
Reviewers: bababuck, hiraditya, RKSimon
Pull Request: https://github.com/llvm/llvm-project/pull/188506
NAS-140361 / 26.0.0-BETA.2 / Fix sysfs reads returning values with trailing newlines (by Qubad786) (#18572)
## Problem
Commit 79a45a9b2b refactored `DiskEntry.__opener` and accidentally
removed the `.strip()` call from sysfs file reads. Sysfs files include a
trailing newline, so without `.strip()`:
- `temp()` — hwmon name reads as `"drivetemp\n"`, which fails the `not
in ("nvme", "drivetemp")` check, so disk temperatures are never
collected
- `media_type` — `"1\n" == "1"` is `False`, so all HDDs are
misclassified as SSD
- `translation` — `"NVMe\n" == "NVMe"` fails, breaking SNTL detection
for NVMe-behind-SAS devices
- `model`, `vendor`, `firmware_revision` — all return with trailing
newlines
## Solution
[7 lines not shown]
NAS-140361 / 26.0.0-BETA.1 / Fix sysfs reads returning values with trailing newlines (by Qubad786) (#18571)
## Problem
Commit 79a45a9b2b refactored `DiskEntry.__opener` and accidentally
removed the `.strip()` call from sysfs file reads. Sysfs files include a
trailing newline, so without `.strip()`:
- `temp()` — hwmon name reads as `"drivetemp\n"`, which fails the `not
in ("nvme", "drivetemp")` check, so disk temperatures are never
collected
- `media_type` — `"1\n" == "1"` is `False`, so all HDDs are
misclassified as SSD
- `translation` — `"NVMe\n" == "NVMe"` fails, breaking SNTL detection
for NVMe-behind-SAS devices
- `model`, `vendor`, `firmware_revision` — all return with trailing
newlines
## Solution
[7 lines not shown]
py-anyio: updated to 4.13.0
4.13.0
- Dropped support for Python 3.9
- Added a ``ttl`` parameter to the ``anyio.functools.lru_cache`` wrapper
- Widened the type annotations of file I/O streams to accept ``IO[bytes]``
instead of just ``BinaryIO``
- Fixed ``anyio.Path`` not being compatible with Python 3.15 due to the removal of
``pathlib.Path.is_reserved()`` and the addition of ``pathlib.Path.__vfspath__()``
- Fixed the ``BrokenResourceError`` raised by the asyncio ``SocketStream`` not having
the original exception as its cause
- Fixed the ``TypeError`` raised when using "func" as a parameter name in
``pytest.mark.parametrize`` when using the pytest plugin
- Fixed the pytest plugin not running tests that had the ``anyio`` marker added
programmatically via ``pytest_collection_modifyitems``
- Fixed cancellation exceptions leaking from a ``CancelScope`` on asyncio when they are
contained in an exception group alongside non-cancellation exceptions
- Fixed ``Condition.wait()`` not passing on a notification when the task is cancelled
[3 lines not shown]
[MLIR] Fix crash in alias printer when encountering null operands (#188581)
When the IR contains operations with null operand values, the
DummyAliasOperationPrinter used during alias collection crashed when
iterating over operand types via op->getOperandTypes(), because
ValueTypeIterator::mapElement calls value.getType() on each operand,
which dereferences null for a null Value.
Fix the crash by:
1. Iterating over operand values directly in printGenericOp, skipping
any null operands.
2. Adding a null-type guard in printType so that null types are silently
skipped.
3. Adding a null-type guard at the top of printAndVisitNestedAliasesImpl
to avoid crashing when visiting sub-elements of a null type.
The test requires using --mlir-very-unsafe-disable-verifier-on-parsing
to construct the invalid IR.
[2 lines not shown]
haproxy: updated to 3.3.6
3.3.6
- BUG/MEDIUM: shctx: Use the next block when data exactly filled a block
- BUG/MINOR: mworker: don't set the PROC_O_LEAVING flag on master process
- BUG/MINOR: tcpcheck: Fix typo in error error message for `http-check expect`
- BUG/MINOR: jws: fix memory leak in jws_b64_signature
- DOC: configuration: http-check expect example typo
- DOC/CLEANUP: config: update mentions of the old "Global parameters" section
- BUG/MEDIUM: ssl: Handle receiving early data with BoringSSL/AWS-LC
- BUG/MINOR: mworker: always stop the receiving listener
- BUG/MEDIUM: ssl: Don't report read data as early data with AWS-LC
- BUG/MINOR: memprof: avoid a small memory leak in "show profiling"
- MINOR: activity: use dynamic allocation for "show profiling" entries
- MINOR: tools: extend the pointer hashing code to ease manipulations
- MINOR: memprof: attempt different retry slots for different hashes on collision
- BUG/MINOR: mworker: only match worker processes when looking for unspawned proc
- BUG/MINOR: mworker: fix typo &= instead of & in proc list serialization
- BUG/MINOR: mworker: set a timeout on the worker socketpair read at startup
[57 lines not shown]
NAS-140361 / 27.0.0-BETA.1 / Fix sysfs reads returning values with trailing newlines (#18570)
## Problem
Commit 79a45a9b2b refactored `DiskEntry.__opener` and accidentally
removed the `.strip()` call from sysfs file reads. Sysfs files include a
trailing newline, so without `.strip()`:
- `temp()` — hwmon name reads as `"drivetemp\n"`, which fails the `not
in ("nvme", "drivetemp")` check, so disk temperatures are never
collected
- `media_type` — `"1\n" == "1"` is `False`, so all HDDs are
misclassified as SSD
- `translation` — `"NVMe\n" == "NVMe"` fails, breaking SNTL detection
for NVMe-behind-SAS devices
- `model`, `vendor`, `firmware_revision` — all return with trailing
newlines
## Solution
[2 lines not shown]
Merge pull request #383 from ghostbsd/dependabot/pip/contrib/libcbor/doc/source/requests-2.33.0
build(deps): bump requests from 2.32.0 to 2.33.0 in /contrib/libcbor/doc/source
