[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230626111344.19136-1-sunliming@kylinos.cn>
Date: Mon, 26 Jun 2023 19:13:41 +0800
From: sunliming <sunliming@...inos.cn>
To: rostedt@...dmis.org, beaub@...ux.microsoft.com, mhiramat@...nel.org
Cc: linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
sunliming <sunliming@...inos.cn>
Subject: [PATCH v4 0/3] tracing/user_events: Fix incorrect return value for writes when events are disabled and add its tests
Now the writing operation return the count of writes regardless of whether
events are enabled or disabled. Fix this by just return -EBADF when events
are disabled.
v3 -> v4:
- Change the return value from zero to -EBADF
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 disabled
selftests/user_events: Enable the event before write_fault test in
ftrace self-test
selftests/user_events: Add test cases when event is disabled
kernel/trace/trace_events_user.c | 3 ++-
tools/testing/selftests/user_events/ftrace_test.c | 8 ++++++++
2 files changed, 10 insertions(+), 1 deletion(-)
--
2.25.1
Powered by blists - more mailing lists