Skip to content

Conversation

@EriComic
Copy link
Contributor

The newer versions of the Linux kernel now check to ensure that QOS mappings also have IFLA_VLAN_QOS_MAPPING set [1]. The kernel will discard QOS atributes where this is not set.

The current libnl code for setting vlan attributes uses variable i to set this parameter. This means that only the second QOS map will be applied since i = 1 = IFLA_VLAN_QOS_MAPPING, the rest will be discarded.

This patch replaces i in the PUT macro to use the already existing enum value IFLA_VLAN_QOS_MAPPING which equals 1.

[1] torvalds/linux@6c21660

Co-authored-by: Daniel Falk [email protected]

The newer versions of the Linux kernel now check to ensure that QOS
mappings also have IFLA_VLAN_QOS_MAPPING set [1]. The kernel will discard
QOS atributes where this is not set.

The current libnl code for setting vlan attributes uses variable i to
set this parameter. This means that only the second QOS map will be
applied since i = 1 = IFLA_VLAN_QOS_MAPPING, the rest will be discarded.

This patch replaces i in the PUT macro to use the already existing enum
value IFLA_VLAN_QOS_MAPPING which equals 1.

[1] torvalds/linux@6c21660

Co-authored-by: Daniel Falk [email protected]
thom311 pushed a commit that referenced this pull request Feb 18, 2025
The newer versions of the Linux kernel now check to ensure that QOS
mappings also have IFLA_VLAN_QOS_MAPPING set [1]. The kernel will discard
QOS atributes where this is not set.

The current libnl code for setting vlan attributes uses variable i to
set this parameter. This means that only the second QOS map will be
applied since i = 1 = IFLA_VLAN_QOS_MAPPING, the rest will be discarded.

This patch replaces i in the PUT macro to use the already existing enum
value IFLA_VLAN_QOS_MAPPING which equals 1.

[1] torvalds/linux@6c21660

Co-authored-by: Daniel Falk [email protected]

#421
@thom311
Copy link
Owner

thom311 commented Feb 18, 2025

lgtm. Merged.

Thank you!

@thom311 thom311 closed this Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants