[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <YmGo/TcNVzOK4Bjn@bombadil.infradead.org>
Date: Thu, 21 Apr 2022 11:57:01 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: mingo@...hat.com, YueHaibing <yuehaibing@...wei.com>,
patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
mcgrof@...nel.org
Subject: [PATCH] ftrace: fix building with SYSCTL=y but DYNAMIC_FTRACE=n
Ok so hopefully this is the last of it. 0day picked up a build
failure [0] when SYSCTL=y but DYNAMIC_FTRACE=n. This can be fixed
by just declaring an empty routine for the calls moved just
recently.
[0] https://lkml.kernel.org/r/202204161203.6dSlgKJX-lkp@intel.com
Reported-by: kernel test robot <lkp@...el.com>
Fixes: f8b7d2b4c192 ("ftrace: fix building with SYSCTL=n but DYNAMIC_FTRACE=y")
Signed-off-by: Luis Chamberlain <mcgrof@...nel.org>
---
kernel/trace/ftrace.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index d9424fd9a183..1f89039f0feb 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -7873,6 +7873,8 @@ int unregister_ftrace_function(struct ftrace_ops *ops)
EXPORT_SYMBOL_GPL(unregister_ftrace_function);
#ifdef CONFIG_SYSCTL
+
+#ifdef CONFIG_DYNAMIC_FTRACE
static void ftrace_startup_sysctl(void)
{
int command;
@@ -7906,6 +7908,10 @@ static void ftrace_shutdown_sysctl(void)
ftrace_run_update_code(command);
}
}
+#else
+# define ftrace_startup_sysctl() do { } while (0)
+# define ftrace_shutdown_sysctl() do { } while (0)
+#endif /* CONFIG_DYNAMIC_FTRACE */
static bool is_permanent_ops_registered(void)
{
--
2.35.1
Powered by blists - more mailing lists