[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230621060827.151564-2-sunliming@kylinos.cn>
Date: Wed, 21 Jun 2023 14:08:24 +0800
From: sunliming <sunliming@...inos.cn>
To: rostedt@...dmis.org, mhiramat@...nel.org, beaub@...ux.microsoft.com
Cc: kelulanainsley@...il.com, linux-trace-kernel@...r.kernel.org,
linux-kernel@...r.kernel.org, sunliming <sunliming@...inos.cn>
Subject: [PATCH v3 1/3] tracing/user_events: Fix incorrect return value for writing operation when events are disable
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.
Signed-off-by: sunliming <sunliming@...inos.cn>
---
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 1ac5ba5685ed..c085ff829a58 100644
--- a/kernel/trace/trace_events_user.c
+++ b/kernel/trace/trace_events_user.c
@@ -1957,7 +1957,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.25.1
Powered by blists - more mailing lists