xdp-loader: Make feature flags printing future-proof #528
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In netdev.h, NETDEV_XDP_ACT_MASK is declared as private, so it should only be used inside the kernel, and according to Jakub Kicinski then "user space should not care about it"[1].
In this specific case, then this code is buggy. If a new feature flag is added to the uapi header, and hence included in NETDEV_XDP_ACT_MASK, and xdp-tools is not updated, or an older version is re-build in a distro, with newer linux headers, then NETDEV_XDP_ACT_MASK can contain a new feature flag, and if the new flag is observed, then it will neither be checked nor trigger the unknown feature printing.
This patch replaces the use of NETDEV_XDP_ACT_MASK, with a local mask consisting only of the tested flags.
[1] https://lore.kernel.org/netdev/[email protected]/