diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2023-06-09 14:53:31 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2023-06-12 11:32:45 +0100 |
| commit | 500e1340d1d2695de3f15fc0b3781f593a77acc2 (patch) | |
| tree | 4d86ba36fb3a24593be237c151aad15439d1bea8 /net/ipv4/tcp_output.c | |
| parent | 5ab8c41cef30d8b6160a80b69d2eb39d570491ac (diff) | |
| download | linux-500e1340d1d2695de3f15fc0b3781f593a77acc2.tar.gz linux-500e1340d1d2695de3f15fc0b3781f593a77acc2.tar.bz2 linux-500e1340d1d2695de3f15fc0b3781f593a77acc2.zip | |
net: ethtool: don't require empty header nests
Ethtool currently requires a header nest (which is used to carry
the common family options) in all requests including dumps.
$ cli.py --spec netlink/specs/ethtool.yaml --dump channels-get
lib.ynl.NlError: Netlink error: Invalid argument
nl_len = 64 (48) nl_flags = 0x300 nl_type = 2
error: -22 extack: {'msg': 'request header missing'}
$ cli.py --spec netlink/specs/ethtool.yaml --dump channels-get \
--json '{"header":{}}'; )
[{'combined-count': 1,
'combined-max': 1,
'header': {'dev-index': 2, 'dev-name': 'enp1s0'}}]
Requiring the header nest to always be there may seem nice
from the consistency perspective, but it's not serving any
practical purpose. We shouldn't burden the user like this.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/tcp_output.c')
0 files changed, 0 insertions, 0 deletions