FWIW, this is the upstream ethtool commit (introduced in v5.7) that adds
support for long names for the -K option:

commit 4b1fa2c2d250441f83b90f9410cd6ce7d879c2fe
Author: Michal Kubecek <[email protected]>
Date:   Mon Apr 13 23:21:20 2020 +0200

    features: accept long legacy flag names when setting features
    
    The legacy feature flags have long names (e.g. "generic-receive-offload")
    and short names (e.g. "gro"). While "ethtool -k" shows only long names,
    "ethtool -K" accepts only short names. This is a bit confusing as users
    have to resort to documentation to see what flag name to use; in
    particular, if a legacy flag corresponds to only one actual kernel feature,
    "ethtool -k" shows the output in the same form as if long flag name were
    a kernel feature name but this name cannot be used to set the flag/feature.
    
    Accept both short and long legacy flag names in "ethool -K".
    
    Reported-by: Konstantin Kharlamov <[email protected]>
    Signed-off-by: Michal Kubecek <[email protected]>
    Signed-off-by: John W. Linville <[email protected]>

https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?id=4b1fa2c2d250441f83b90f9410cd6ce7d879c2fe

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2136734

Title:
  selftests: net: veth: fix compatibility with older ethtool versions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2136734/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to