When calling the callback v2 for objects that were updated, we pass the update ("obj") instead of the updated object ("old") as new.
Presumably this wasn't intended, so pass the updated object as new.
This avoids weird updates where the new object is significantly smaller than the old one. E.g. for IPv6 multipath route updates, old would be the full route with all nexthops, while new would be a partial route with only the added/removed nexthop.
Fixes: 66d032ad443a ("cache_mngr: add include callback v2")
thom311
commented
4 months ago
When calling the callback v2 for objects that were updated, we pass the update ("obj") instead of the updated object ("old") as new.
Presumably this wasn't intended, so pass the updated object as new.
This avoids weird updates where the new object is significantly smaller than the old one. E.g. for IPv6 multipath route updates, old would be the full route with all nexthops, while new would be a partial route with only the added/removed nexthop.
Fixes: 66d032ad443a ("cache_mngr: add include callback v2")