On 3/16/26 5:26 AM, Hangbin Liu wrote: > Currently, master devices (bonding, bridge, team) manually call > netdev_compute_master_upper_features() scattered throughout their port > add/remove operations. This approach requires each driver to remember > to update features at the right times and leads to code duplication. > > The series adds a new ndo_update_offloads callback that is automatically > invoked during feature updates when upper/lower device relationships change. > This centralizes the feature computation flow and removes the burden > from individual drivers.
I'm sorry for the late feedback, but I think the driver cleanup and simplification is not worthy the core complexity and the new NDO added. The AI reported issue would probably need very non trivial changes to both team and bond driver to be addressed. Most of the cleanups belong to netdev_compute_master_upper_features() introduction in the failover driver. Factoring out that single change would be IMHO a better option, if possible. The new ndo looks controversial. We already have 2 different ndo at __netdev_update_features() time, with slightly different semantic. Adding another one feels like a design issue. /P
