From: Steven Rostedt <rostedt@goodmis.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: zhengyejian1@huawei.com, akaher@vmware.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, mhiramat@kernel.org,
shuah@kernel.org, skhan@linuxfoundation.org,
yeweihua4@huawei.com
Subject: Re: "[PATCH] selftests/ftrace: Correctly enable event in instance-event.tc"
Date: Wed, 6 Sep 2023 18:46:50 -0400 [thread overview]
Message-ID: <20230906184650.074dfdcf@gandalf.local.home> (raw)
In-Reply-To: <20230906145000.29291a1b@gandalf.local.home>
On Wed, 6 Sep 2023 14:50:00 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> BTW, when you ran these, did you apply:
>
> https://patchwork.kernel.org/project/linux-trace-kernel/patch/20230905183332.628d7cc0@gandalf.local.home/
Can you both try the above patch and this patch?
-- Steve
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 35783a7baf15..0827037ee3b8 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -4973,6 +4973,33 @@ int tracing_open_generic_tr(struct inode *inode, struct file *filp)
return 0;
}
+/*
+ * The private pointer of the inode is the trace_event_file.
+ * Update the tr ref count associated to it.
+ */
+int tracing_open_file_tr(struct inode *inode, struct file *filp)
+{
+ struct trace_event_file *file = inode->i_private;
+ int ret;
+
+ ret = tracing_check_open_get_tr(file->tr);
+ if (ret)
+ return ret;
+
+ filp->private_data = inode->i_private;
+
+ return 0;
+}
+
+int tracing_release_file_tr(struct inode *inode, struct file *filp)
+{
+ struct trace_event_file *file = inode->i_private;
+
+ trace_array_put(file->tr);
+
+ return 0;
+}
+
static int tracing_mark_open(struct inode *inode, struct file *filp)
{
stream_open(inode, filp);
diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
index 5669dd1f90d9..77debe53f07c 100644
--- a/kernel/trace/trace.h
+++ b/kernel/trace/trace.h
@@ -610,6 +610,8 @@ void tracing_reset_all_online_cpus(void);
void tracing_reset_all_online_cpus_unlocked(void);
int tracing_open_generic(struct inode *inode, struct file *filp);
int tracing_open_generic_tr(struct inode *inode, struct file *filp);
+int tracing_open_file_tr(struct inode *inode, struct file *filp);
+int tracing_release_file_tr(struct inode *inode, struct file *filp);
bool tracing_is_disabled(void);
bool tracer_tracing_is_on(struct trace_array *tr);
void tracer_tracing_on(struct trace_array *tr);
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index ed367d713be0..2af92177b765 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -2103,9 +2103,10 @@ static const struct file_operations ftrace_set_event_notrace_pid_fops = {
};
static const struct file_operations ftrace_enable_fops = {
- .open = tracing_open_generic,
+ .open = tracing_open_file_tr,
.read = event_enable_read,
.write = event_enable_write,
+ .release = tracing_release_file_tr,
.llseek = default_llseek,
};
@@ -2122,9 +2123,10 @@ static const struct file_operations ftrace_event_id_fops = {
};
static const struct file_operations ftrace_event_filter_fops = {
- .open = tracing_open_generic,
+ .open = tracing_open_file_tr,
.read = event_filter_read,
.write = event_filter_write,
+ .release = tracing_release_file_tr,
.llseek = default_llseek,
};
--
2.40.1
next prev parent reply other threads:[~2023-09-06 22:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 0:11 [PATCH] selftests/ftrace: Correctly enable event in instance-event.tc Zheng Yejian
2023-06-26 10:11 ` Masami Hiramatsu
2023-06-26 10:12 ` Masami Hiramatsu
2023-07-10 22:37 ` Steven Rostedt
2023-09-05 12:54 ` Zheng Yejian
2023-09-05 16:25 ` Steven Rostedt
2023-09-05 16:49 ` Steven Rostedt
2023-09-05 18:45 ` Steven Rostedt
2023-09-05 20:32 ` Steven Rostedt
2023-09-06 1:26 ` Zheng Yejian
2023-09-05 22:36 ` Steven Rostedt
2023-09-06 1:42 ` Zheng Yejian
2023-09-06 11:27 ` Steven Rostedt
2023-09-06 11:57 ` Zheng Yejian
2023-09-06 12:56 ` Steven Rostedt
2023-09-06 13:02 ` Steven Rostedt
2023-09-06 13:31 ` Zheng Yejian
2023-09-06 13:43 ` Steven Rostedt
2023-09-06 13:45 ` Steven Rostedt
2023-09-06 14:01 ` Zheng Yejian
2023-09-06 14:04 ` Steven Rostedt
2023-09-05 22:43 ` Shuah Khan
2023-09-06 1:45 ` Zheng Yejian
2023-09-06 14:26 ` "[PATCH] selftests/ftrace: Correctly enable event in instance-event.tc" Naresh Kamboju
2023-09-06 14:37 ` Steven Rostedt
2023-09-06 21:37 ` Steven Rostedt
2023-09-07 1:01 ` Zheng Yejian
2023-09-06 18:50 ` Steven Rostedt
2023-09-06 22:46 ` Steven Rostedt [this message]
2023-09-07 1:39 ` Zheng Yejian
2023-09-07 1:44 ` 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:
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=20230906184650.074dfdcf@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akaher@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=yeweihua4@huawei.com \
--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
all inboxes | Powered by JetHome®