devlink: Fix TP_STRUCT_entry in trace of devlink health report
authorMoshe Shemesh <moshe@nvidia.com>
Tue, 14 Feb 2023 16:38:06 +0000 (18:38 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 10 Mar 2023 08:33:54 +0000 (09:33 +0100)
[ Upstream commit d0ab772c1f1558af84f3293a52e9e886e08e0754 ]

Fix a bug in trace point definition for devlink health report, as
TP_STRUCT_entry of reporter_name should get reporter_name and not msg.

Note no fixes tag as this is a harmless bug as both reporter_name and
msg are strings and TP_fast_assign for this entry is correct.

Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
include/trace/events/devlink.h

index 2496918..77ff7cf 100644 (file)
@@ -88,7 +88,7 @@ TRACE_EVENT(devlink_health_report,
                __string(bus_name, devlink_to_dev(devlink)->bus->name)
                __string(dev_name, dev_name(devlink_to_dev(devlink)))
                __string(driver_name, devlink_to_dev(devlink)->driver->name)
-               __string(reporter_name, msg)
+               __string(reporter_name, reporter_name)
                __string(msg, msg)
        ),