diff options
| author | Maxime Chevallier <[email protected]> | 2025-03-01 14:11:13 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2025-03-05 01:12:01 +0000 |
| commit | 637399bf7e77797811adf340090b561a8f9d1213 (patch) | |
| tree | 01b602cf50470b312205b0f9d6e7e970fb6bb331 /tools/perf/scripts/python/libxed.py | |
| parent | ppp: Fix KMSAN uninit-value warning with bpf (diff) | |
| download | kernel-637399bf7e77797811adf340090b561a8f9d1213.tar.gz kernel-637399bf7e77797811adf340090b561a8f9d1213.zip | |
net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device
ethnl_req_get_phydev() is used to lookup a phy_device, in the case an
ethtool netlink command targets a specific phydev within a netdev's
topology.
It takes as a parameter a const struct nlattr *header that's used for
error handling :
if (!phydev) {
NL_SET_ERR_MSG_ATTR(extack, header,
"no phy matching phyindex");
return ERR_PTR(-ENODEV);
}
In the notify path after a ->set operation however, there's no request
attributes available.
The typical callsite for the above function looks like:
phydev = ethnl_req_get_phydev(req_base, tb[ETHTOOL_A_XXX_HEADER],
info->extack);
So, when tb is NULL (such as in the ethnl notify path), we have a nice
crash.
It turns out that there's only the PLCA command that is in that case, as
the other phydev-specific commands don't have a notification.
This commit fixes the crash by passing the cmd index and the nlattr
array separately, allowing NULL-checking it directly inside the helper.
Fixes: c15e065b46dc ("net: ethtool: Allow passing a phy index for some commands")
Signed-off-by: Maxime Chevallier <[email protected]>
Reviewed-by: Kory Maincent <[email protected]>
Reported-by: Parthiban Veerasooran <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/libxed.py')
0 files changed, 0 insertions, 0 deletions
