[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230628125448.007243475@goodmis.org>
Date: Wed, 28 Jun 2023 08:54:48 -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>
Subject: [for-linus][PATCH 0/3] tracing: Final updates for 6.4+
The user events write currently returns the size of what was suppose to be
written when tracing is disabled and nothing was written. Instead, behave like
trace_marker and return -EBADF, as that is what is returned if a file is opened
for read only,
Before user events become an ABI, fix the return value of the write
operation when tracing is disabled. It should not return an error, but
simply report it wrote zero bytes. Just like any other write operation
that doesn't write but does not "fail".
This also includes test cases for this use case.
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent
Head SHA1: e155047e53d25f09d055c08ae9d6c269520e90d8
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(-)
Powered by blists - more mailing lists