From: Petr Pavlu <petr.pavlu@suse.com>
To: rostedt@goodmis.org, mhiramat@kernel.org, mathieu.desnoyers@efficios.com
Cc: zhengyejian1@huawei.com, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org, Petr Pavlu <petr.pavlu@suse.com>
Subject: [PATCH 2/2] tracing: Disable events in reverse order of their enable operation
Date: Mon, 27 Nov 2023 16:12:48 +0100 [thread overview]
Message-ID: <20231127151248.7232-3-petr.pavlu@suse.com> (raw)
In-Reply-To: <20231127151248.7232-1-petr.pavlu@suse.com>
Make the disable operation in __ftrace_event_enable_disable() use the
reverse order of the respective enable operation.
This has two minor benefits:
* Disabling of buffered events via trace_buffered_event_disable() is
done after unregistering the trace event. It closes a small window
where an event would be still registered and could be hit, but would
unnecessarily go directly to a ring buffer.
* The SOFT_DISABLED flag is now consistently set only when SOFT_MODE is
also set.
Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
---
kernel/trace/trace_events.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index f29e815ca5b2..5f14d68a0ced 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -633,9 +633,6 @@ static int __ftrace_event_enable_disable(struct trace_event_file *file,
if (atomic_dec_return(&file->sm_ref) > 0)
break;
disable = file->flags & EVENT_FILE_FL_SOFT_DISABLED;
- clear_bit(EVENT_FILE_FL_SOFT_MODE_BIT, &file->flags);
- /* Disable use of trace_buffered_event */
- trace_buffered_event_disable();
} else
disable = !(file->flags & EVENT_FILE_FL_SOFT_MODE);
@@ -653,11 +650,17 @@ static int __ftrace_event_enable_disable(struct trace_event_file *file,
call->class->reg(call, TRACE_REG_UNREGISTER, file);
}
- /* If in SOFT_MODE, just set the SOFT_DISABLE_BIT, else clear it */
- if (file->flags & EVENT_FILE_FL_SOFT_MODE)
- set_bit(EVENT_FILE_FL_SOFT_DISABLED_BIT, &file->flags);
- else
+
+ if (soft_disable) {
+ /* Complete going out of SOFT_MODE */
clear_bit(EVENT_FILE_FL_SOFT_DISABLED_BIT, &file->flags);
+ clear_bit(EVENT_FILE_FL_SOFT_MODE_BIT, &file->flags);
+ /* Disable use of trace_buffered_event */
+ trace_buffered_event_disable();
+ } else if (file->flags & EVENT_FILE_FL_SOFT_MODE) {
+ /* If in SOFT_MODE, just set the SOFT_DISABLE_BIT */
+ set_bit(EVENT_FILE_FL_SOFT_DISABLED_BIT, &file->flags);
+ }
break;
case 1:
/*
--
2.35.3
next prev parent reply other threads:[~2023-11-27 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:12 [PATCH 0/2] tracing: Simplify and fix "buffered event" synchronization Petr Pavlu
2023-11-27 15:12 ` [PATCH 1/2] " Petr Pavlu
2023-11-27 17:41 ` Steven Rostedt
2023-11-28 15:05 ` Petr Pavlu
2023-11-28 15:27 ` Steven Rostedt
2023-11-29 9:22 ` Petr Pavlu
2023-11-29 14:58 ` Steven Rostedt
2023-12-01 14:17 ` Petr Pavlu
2023-12-01 14:46 ` Steven Rostedt
2023-12-05 16:16 ` Petr Pavlu
2023-11-27 15:12 ` Petr Pavlu [this message]
2023-11-27 17:58 ` [PATCH 2/2] tracing: Disable events in reverse order of their enable operation Steven Rostedt
2023-11-28 15:06 ` Petr Pavlu
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231127151248.7232-3-petr.pavlu@suse.com \
--to=petr.pavlu@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=zhengyejian1@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox