[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230623013335.974523605@goodmis.org>
Date: Thu, 22 Jun 2023 21:31:53 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Masami Hiramatsu <mhiramat@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
sunliming <sunliming@...inos.cn>,
Beau Belgrave <beaub@...ux.microsoft.com>
Subject: [for-linus][PATCH 1/3] tracing/user_events: Fix incorrect return value for writing operation
when events are disabled
From: sunliming <sunliming@...inos.cn>
The writing operation return the count of writes regardless of whether events
are enabled or disabled. Switch it to return 0 to indicates that the event
is disabled.
Link: https://lore.kernel.org/linux-trace-kernel/20230621060827.151564-2-sunliming@kylinos.cn
Signed-off-by: sunliming <sunliming@...inos.cn>
Acked-by: Beau Belgrave <beaub@...ux.microsoft.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@...dmis.org>
---
kernel/trace/trace_events_user.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events_user.c b/kernel/trace/trace_events_user.c
index 8df0550415e7..902cae005df4 100644
--- a/kernel/trace/trace_events_user.c
+++ b/kernel/trace/trace_events_user.c
@@ -2096,7 +2096,8 @@ static ssize_t user_events_write_core(struct file *file, struct iov_iter *i)
if (unlikely(faulted))
return -EFAULT;
- }
+ } else
+ return 0;
return ret;
}
--
2.39.2
Powered by blists - more mailing lists