[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230609030302.1278716-1-sunliming@kylinos.cn>
Date:   Fri,  9 Jun 2023 11:02:59 +0800
From:   sunliming <sunliming@...inos.cn>
To:     mhiramat@...nel.org, beaub@...ux.microsoft.com,
        rostedt@...dmis.org, shuah@...nel.org
Cc:     linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
        linux-kselftest@...r.kernel.org, kelulanainsley@...il.com,
        sunliming <sunliming@...inos.cn>
Subject: [PATCH v2 0/3] tracing/user_events: Fix incorrect return value for
Now the writing operation return the count of writes whether events are
enabled or disabled. Fix this by just return -ENOENT when events are disabled.
v1 -> v2:
- Change the returh vale 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
 
