[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230621060827.151564-1-sunliming@kylinos.cn>
Date: Wed, 21 Jun 2023 14:08:23 +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 0/3] tracing/user_events: Fix incorrect return value for
Now the writing operation return the count of writes regardless of whether
events are enabled or disabled. Fix this by just return zero when events
are disabled.
v2 -> v3:
- Change the return value from -ENOENT to zero
v1 -> v2:
- Change the return value from -EFAULT to -ENOENT
sunliming (3):
tracing/user_events: Fix incorrect return value for writing operation
when events are disable
selftests/user_events: Enable the event before write_fault test in
ftrace self-test
selftests/user_events: Add test cases when event is diabled
kernel/trace/trace_events_user.c | 3 ++-
tools/testing/selftests/user_events/ftrace_test.c | 7 +++++++
2 files changed, 9 insertions(+), 1 deletion(-)
--
2.25.1
Powered by blists - more mailing lists