System: Snapshots - always enforce note directory to be owned by "wwwonly:wheel" as configured to prevent notes created by the ui in root mode not being readable when switching to wwwonly.
(cherry picked from commit f81d527a436e5376cbac112ac444a5e54b7fdc93)
System: Snapshots - always enforce note directory to be owned by "wwwonly:wheel" as configured to prevent notes created by the ui in root mode not being readable when switching to wwwonly.
devel/py-pydbus: Switch to USE_PYTHON=pep517
Build with the PEP 517 frontend (setuptools legacy backend; the source
has no [build-system]); the package metadata becomes dist-info.
PR: 300055
Revert "System: Snapshots - always enforce notes to be owned by wwwonly to prevent notes created by the ui in root mode not being readable when switching to wwwonly."
This reverts commit b2fb2b63f479c8879d9a54fefabe310712cefd70.
use upstream e230f474b87134e8c6c85b630084c612057f253e and fix ia64 builds.
upstream commit message:
disable BROTLI_MODEL macro for some targets
PiperOrigin-RevId: 827486322
pci: Reserve bus numbers required by SR-IOV VFs
Some firmware assigns only one bus number to each PCI-PCI bridge. This
prevents later SR-IOV VF enumeration when a VF routing ID falls on a bus
number already allocated to a sibling bridge.
Reserve only the additional bus numbers required by SR-IOV PFs.
Enumerate all directly attached functions before child drivers and
bridges attach, inspect their device_t objects for SR-IOV, and grow the
PCI bus resource through the highest possible VF routing ID.
First VF Offset and VF Stride may change when NumVFs changes. Probe
every valid NumVFs value and preserve the original setting. When the
upstream hierarchy uses ARI, temporarily enable the SR-IOV ARI Hierarchy
control in the lowest-numbered PF while sizing, then restore it. Scope
active-VF detection to each conventional PCI slot; an ARI bus remains
one slot-0 hierarchy. If firmware left VFs enabled on a device, do not
modify it and reserve only its active layout.
[21 lines not shown]
pci_iov: Reuse downstream bridge bus window if it already covers VF bus
If the parent bridge's [secondary, subordinate] window already covers
the VF bus (e.g., programmed by BIOS or a prior PF), skip allocating
PCI_RES_BUS. This avoids a duplicate rman allocation in the multi-PF
case while still allocating when growth is actually needed.
Reviewed by: ssaxena
Differential Revision: https://reviews.freebsd.org/D52163
(cherry picked from commit feb0a7e19f3c2e4c7eb90668b1e3dc34b5bb6dd6)
System: Snapshots - always enforce notes to be owned by wwwonly to prevent notes created by the ui in root mode not being readable when switching to wwwonly.
[mlir] Move bufferization external models into their own libraries (#236459)
Prior to this PR the external models for `BufferizableOpInterface`,
`BufferDeallocationOpInterface`, `BufferViewFlowOpInterface` and
`AllocationOpInterface` lived in each dialect's Transforms library.
Every user of an unrelated transform therefore depended on the
Bufferization dialect and transforms.
This PR moves each model into its own `MLIR<Dialect><Interface>Impl`
library such that only users of those library requires dependent
libraries to be built. In particular, the Arith, ControlFlow, GPU,
MLProgram, SCF and Shape Transforms libraries no longer link
MLIRBufferizationDialect or MLIRBufferizationTransforms and
MLIRTensorTransforms no longer links MLIRLinalgDialect. This gives 104
targets a smaller link closure, e.g. MLIRControlFlowTransforms (-22
libraries), MLIRMLProgramTransforms (-20), MLIRSCFTransforms (-8) and
MLIRTensorTransforms (-7).
The Linalg model and the Func model in MLIRBufferizationTransforms stay
[6 lines not shown]
[ARM] Ignore register tuples when emitting CodeView locations (#222347)
CodeView has register numbers for ARM's core, status, S, D and Q
registers, but none for the synthetic register tuples. A variable
assigned to one -- for example the odd-even D pair D1_D2 -- reached
getCodeViewRegNum and aborted the whole object file with "unknown
codeview register D1_D2".
Override isIgnoredCVReg for ARM so those registers are skipped, as
AArch64 already does for SVE Z and P registers. The variable is still
emitted and reports as optimized out. No register number would be
correct for a tuple, and naming one half of it would put the debugger in
the wrong place.
The check names the tuple register classes rather than treating every
unmapped register as ignorable, so a mapping that is genuinely missing
still reports an error instead of being dropped silently.
DPair contains the Q registers as well as the odd-even D pairs, so QPR
is excluded from the check; the qreg variable in the test is the control
that would catch losing them.
[3 lines not shown]
ixl(4): Fix NVM update API
Driver provides an interface for tools operating on adapters'
Non-Volatile Memory using SIOC(G|S)DRVSPEC ioctls. It allows
tools to issue Admin Queue commands to the firmware, which
may return an error code encoded as a negative integer.
The driver passed this negative integer as the return value
of the ioctl handler. This was causing issues because the FreeBSD
kernel reserves negative error codes in system calls for special
purposes such as restarting the handler or detecting incorrect
behavior in VFS operations. Simple remapping of negative values
to positive integers caused currently available tools to misbehave
and could break the NVM update process. Introduce a new API version,
which allows new versions of tools to detect the fixed driver.
Temporarily keep the old API, but issue a warning that tools need
to be updated.
Also refactor the code to use centralized cleanup and move the
debug message from the firmware earlier to make sure it is not masked
[10 lines not shown]
cxgbe(4): Fix netmap rx behavior with nm_split_rss
The driver should look for active queues and one potential default-queue
in both halves of the split instead of stopping at the first valid
default-queue.
Fixes: a9f476580eb0cxgbe(4): fixes for netmap operation with only some queues active
Sponsored by: Chelsio Communications
(cherry picked from commit 77d71f5f36cc01e7fc2ca0828af00a4478bbf53c)
em(4): fix capability bounds needed to access checksum context.
Ensure the offp capability bounds cover entire struct with checksum fields.
This is needed for CHERI systems to avoid bounds violation trap, as
otherwise offp allowed to dereference 4 bytes of csum_flags field only
so bzero failed.
Tested on ARM Morello.
Reviewed by: kbowling
Discussed with: jrtc27
Sponsored by: CHERI Research Centre
Differential Revision: https://reviews.freebsd.org/D53903
(cherry picked from commit 64ee9c166ce5e807e575d205ac2e15cc5cf6581b)
vtnet: remove M_HASHTYPE when there is only one pair of rx/tx queue
Summary:
Doing so will let the upper layer know how to deal with software hash,
with benefits like inp_flowid can be set and m_pkthdr.flowid can be set
in output path.
Reviewed by: tuexen
Differential Revision: https://reviews.freebsd.org/D54929
(cherry picked from commit 20285cad7a55ecd0020f51f3daee74db8b1ea5a0)
Revert "fetch: download packages concurrently with repository limits"
This reverts commit d7a9f380aaa0e1a3cb2945ba676036cfe9fff97d.
This is a too naive implementation, this will be reworked post 2.9.0 is
out
among the issue:
- default limit per host should be 1
- the limit should not be per repo but per host
- in case of multi repository, on the same host, number of // wokrers
should be shared
- no backoff mecanism (with retry-after support)
- no share memory of errors, per host, so a host cannot be excluded
of the list in case of failures.
