All of
 help / color / mirror / Atom feed
From: Steven Rostedt <>
To: LKML <>
Cc: Beau Belgrave <>,
	Masami Hiramatsu <>,
	linux-trace-devel <>,
	bpf <>,
	Network Development <>,
	Mathieu Desnoyers <>,
	Alexei Starovoitov <>,
	Linus Torvalds <>
Subject: [PATCH v2] tracing: Set user_events to BROKEN
Date: Wed, 30 Mar 2022 15:58:35 -0400	[thread overview]
Message-ID: <20220330155835.5e1f6669@gandalf.local.home> (raw)

From: "Steven Rostedt (Google)" <>

After being merged, user_events become more visible to a wider audience
that have concerns with the current API. It is too late to fix this for
this release, but instead of a full revert, just mark it as BROKEN (which
prevents it from being selected in make config). Then we can work finding
a better API. If that fails, then it will need to be completely reverted.


Signed-off-by: Steven Rostedt (Google) <>
Changes since v1:
 - Add depends on COMPILE_TEST too (Linus Torvalds)

 Hopefully, no distro is idiotic enough to enable COMPILE_TEST in their
 builds to get this feature.

 kernel/trace/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 16a52a71732d..f83d29adb375 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -741,6 +741,7 @@ config USER_EVENTS
 	bool "User trace events"
 	select TRACING
+	depends on BROKEN || COMPILE_TEST # API needs to be straighten out
 	  User trace events are user-defined trace events that
 	  can be used like an existing kernel trace event.  User trace

             reply	other threads:[~2022-03-30 19:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 19:58 Steven Rostedt [this message]
2022-04-03 14:39 ` [PATCH v2] tracing: Set user_events to BROKEN Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220330155835.5e1f6669@gandalf.local.home \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.