use an smr crit section instead of real iface refs in the uRPF check
the uRPF tries to use interface indexes, but if the index doesnt
match it'll resolve to a real interface and do an IFT_CARP and
carpdev index check.
it's easy to do this lookup from an smr crit section and avoid the
refcnt ops.
use an smr crit section instead of real interface refs in pf_match_rcvif
this is only used during ruleset evaluation, so it is less hot than
the carpdev resolution done in pf_test, but it's an easy change to
avoid unecessary atomic ops.
use an smr crit section to get the parent of carp interfaces.
pf maps packets "received" on carp interfaces back to the actual
interface it was received on and applies policy to that parent.
eg, if you have carp0 on top of em0, packets destined to the carp0
mac address, the network stack will think that the packets were
received by carp0. pf maps carp0 back to em0 and applies policy on
em0 though.
previously pf used if_get/if_put to do this lookup of the carp
parent, which is a couple of atomic ops on what can be a contended
cacheline for every packet destined for a carp interface. now the
lookup is done in an SMR critical section, against what will
hopefully be a shared cacheline.
update py-pydantic and py-pydantic-core for Python 3.14 support
The current version of pydantic-core uses a pyo3 that is too old.
tested by and ok MAINTAINER
QtQml: Invalidate fallback lookups after each call from AOT code
Fallback property lookups are created for completely dynamic
metaobjects. Anything about them may change between any two calls.
Pick-to: 6.8 6.5
Fixes: QTBUG-142331
Change-Id: Ib732c37a6f27ab8105bea0eeae000af7eb9c36d7
Reviewed-by: Sami Shalayel <sami.shalayel at qt.io>
(cherry picked from commit 9af6d2d6d0046b3c8369e15eb4791957cdc7ab7b)
Reviewed-by: Fabian Kosmale <fabian.kosmale at qt.io>
