On Thu, 19 Dec 2024 18:39:26 +0100 Daniel Borkmann wrote:
> + if (headroom) {
> + peer->needed_headroom = headroom;
> + dev->needed_headroom = headroom;
> + }
> + if (tailroom) {
> + peer->needed_tailroom = tailroom;
> + dev->needed_tailroom = tailroom;
> + }
Since you use the same one for main dev and peer should there be
something rejecting the use of the new attr in the peer attrs?
(IFLA_NETKIT_PEER_INFO)
> + struct {
static const?
I wish more userspace learned how to do reverse parsing.
We wouldn't have to bother injecting the attr names to all the messages,
NL_SET_ERR_MSG_ATTR() already points to the attr :|
