interface: POC for multi-dhcp6c support
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
At the moment this splits off dhcp6c only but we need to
change the daemon's print a bit to avoid complaining about
"other" devices since the situation to ignore a non-listening
interface is normal and not "ignoring" something obvious as
the INFO log message suggests.
Remove the $id bootstrapping now that every service has its
own configuration and "0" cannot overlap and add some options
relavant to #7647.
rtsold still needs to be split to allow for HUP reload of
a single interface instead of forcing a restart of all
DHCPv6 WAN clients at the same time.
interfaces: introduce idassoc6 mode #9155
We're adding a bit of technical debt here for the simple reason
to decouple the track6 mode from automatic radvd and dhcpv6 runs.
Specifically avoid the "dhcpd6track6allowoverride" flag in this
mode but keep the data the same otherwise for interoperability.
[IR] Fix Module move-assignment missing NamedMDSymTab, ComdatSymTab and Parent update (#175501)
`Module::operator=(Module&&)` had three bugs:
1. `NamedMDSymTab` was not moved, may causing getNamedMetadata() to
fail.
2. `ComdatSymTab` was not moved, may causing getOrInsertComdat() to
fail.
3. `NamedMDNode::Parent` was not updated after splice, may causing
getParent() to return the wrong Module.
[SystemZ][z/OS] Handle labels for parts (#175665)
Global data is emitted into parts, which are modelled as a MCSection. A
label (symbol of type LD) is not allowed in a part, which requires
special handling. The approach is to not emit the label at all, and
using the part symbol in relocations.
pipewire: define __LOCALE_C_ONLY in spa/utils/string.h on NetBSD
Avoid requiring 'CFLAGS.NetBSD+= -D__LOCALE_C_ONLY' in all
packages that include PipeWire public headers
Tested with wip/xdg-desktop-portal
vm_object: remove the charge member
State that the object charge is zero if object->cred == NULL, or equal
to the ptoa(object->size) otherwise.
Besides being much simpler, the transition to use object->size corrects
the architectural issue with the use of object->charge. The split
operations effectively carve the holes in the charged regions, but
single counter cannot properly express it. As result, coalescing
anonymous mappings cannot calculate correctly if the extended mapping
already backed by the existing object is already accounted or not [1].
To properly solve the issue, either we need to start tracking exact
charged regions in the anonymous objects, which has the significant
overhead and complications. Or give up on the slight over-accounting
and charge the whole object unconditionally, as it is done in the patch.
Reported by: mmel, pho [1]
Reviewed by: markj
[4 lines not shown]
rfork(2): fix swap accounting in vmspace_unshare()
When an attempt to increase the swap charge for the ucred failed, we
must forcibly increase the charge to allow the vmspace_destroy()
operation to correctly un-charge the accumulated objects.
Add a swap_reserve_force_by_cred() helper and use it in
vmspace_unshare(), same as it is done in normal fork operations.
Reviewed by: markj
Tested by: pho
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D54572
tuning.7: add more explanation about swap (over-)accounting
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D54572
swap_release_by_cred*(): give some additional info on panics due to underflow
Reviewed by: markj
Tested by: pho
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D54572
NAS-139261 / 26.04 / Make all `zfs.resource` calls type-safe (#17998)
A continuation of the work that I started in
https://github.com/truenas/middleware/pull/17805. Now, the whole
truenas_pylibzfs part of ZFS plugin is called in a type-safe manner.
AMDGPU: Directly use v2bf16 as register type for bf16 vectors.
Previously we were casting v2bf16 to i32, unlike the f16 case. Simplify
this by using the natural vector type. This is probably a leftover from
before v2bf16 was treated as legal. This is preparation for fixing a
miscompile in globalisel.
[X86][NewPM] Port x86-argument-stack-slot (#175659)
Standard porting. Refactor runOnMachineFunction to a static function,
and then wrap it in the legacy/new PMs. Rename the pass to be consistent
with other backend passes.
