tracing: Final updates for 6.4+
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | tracing/user_events: Fix incorrect return value for writing operation when events are disabledkernel/ | +2 | 0 replies | |
| 2/3 | selftests/user_events: Enable the event before write_fault test in ftrace self-testtools/ | +4 | 0 replies | |
| 3/3 | selftests/user_events: Add test cases when event is disabledtools/ | +4 | 0 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Beau Belgrave |
|---|---|
| 1/3 | A-b |
| 2/3 | A-b |
| 3/3 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [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(-)