Re: [PATCH net-next 3/5] selftests: drv-net: check tcp-data-split against an already attached XDP

On 09/28, Jakub Kicinski wrote:

hds.py only ever tested one direction of the rule: with header-data
split on, installing a single-buffer XDP program must fail. The other
direction was not covered at all, and that is the one which was broken
for a program an upper device pushed down - the device was running XDP
but nothing in the core knew, so enabling tcp-data-split underneath it
succeeded.

xdp_set_hds() covers the direct case, xdp_bond_set_hds() the propagated
one. The latter fails without the preceding fix.

The bond case is disruptive, it takes the device down to enslave it, and
skips on devices bonding will not take as an XDP slave.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Acked-by: Stanislav Fomichev <sdf@fomichev.me>