From: Vincent Donnefort <vdonnefort@google.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
linux-trace-kernel@vger.kernel.org
Cc: mathieu.desnoyers@efficios.com, kernel-team@android.com,
linux-kernel@vger.kernel.org,
Vincent Donnefort <vdonnefort@google.com>
Subject: [PATCH v3 03/18] tracing/remotes: Use kstrtobool for boolean tracefs files
Date: Tue, 21 Jul 2026 11:35:48 +0100 [thread overview]
Message-ID: <20260721103603.342266-4-vdonnefort@google.com> (raw)
In-Reply-To: <20260721103603.342266-1-vdonnefort@google.com>
Use kstrtobool in trace_remote.c where possible. This is more user-friendly
as it allows a better variety of input strings.
Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
diff --git a/kernel/trace/trace_remote.c b/kernel/trace/trace_remote.c
index 2bc3afe1204c..94a52445cff9 100644
--- a/kernel/trace/trace_remote.c
+++ b/kernel/trace/trace_remote.c
@@ -235,10 +235,10 @@ tracing_on_write(struct file *filp, const char __user *ubuf, size_t cnt, loff_t
{
struct seq_file *seq = filp->private_data;
struct trace_remote *remote = seq->private;
- unsigned long val;
+ bool val;
int ret;
- ret = kstrtoul_from_user(ubuf, cnt, 10, &val);
+ ret = kstrtobool_from_user(ubuf, cnt, &val);
if (ret)
return ret;
@@ -1148,10 +1148,10 @@ static ssize_t remote_event_enable_write(struct file *filp, const char __user *u
struct seq_file *seq = filp->private_data;
struct remote_event *evt = seq->private;
struct trace_remote *remote = evt->remote;
- u8 enable;
+ bool enable;
int ret;
- ret = kstrtou8_from_user(ubuf, count, 10, &enable);
+ ret = kstrtobool_from_user(ubuf, count, &enable);
if (ret)
return ret;
@@ -1232,10 +1232,10 @@ static ssize_t remote_events_dir_enable_write(struct file *filp, const char __us
size_t count, loff_t *ppos)
{
struct trace_remote *remote = file_inode(filp)->i_private;
+ bool enable;
int i, ret;
- u8 enable;
- ret = kstrtou8_from_user(ubuf, count, 10, &enable);
+ ret = kstrtobool_from_user(ubuf, count, &enable);
if (ret)
return ret;
--
2.55.0.229.g6434b31f56-goog
next prev parent reply other threads:[~2026-07-21 10:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 10:35 [PATCH v3 00/18] tracing/remotes: Add printk, dump_on_panic and boot parameters Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 01/18] tracing/remotes: Gate tracefs files opening on trace remote registration Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 02/18] tracing/remotes: Release tracefs,eventfs on registration failure Vincent Donnefort
2026-07-21 10:35 ` Vincent Donnefort [this message]
2026-07-21 10:35 ` [PATCH v3 04/18] tracing/remotes: Use a single per-remote polling work Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 05/18] tracing/simple_ring_buffer: Add support for compressed length Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 06/18] tracing/remotes: Add dmesg tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 07/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 08/18] tracing/remotes: selftests: Prefix hypervisor folder Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 09/18] ring-buffer: Use irqsave for the reader lock in ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 10/18] ring-buffer: Use panic-friendly locking in ring_buffer_iter interface Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 11/18] ring-buffer: Add ring_buffer_read_remote_meta_page() Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 12/18] ring-buffer: Add kerneldoc for ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 13/18] tracing/remotes: Add dump_on_panic tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 14/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 15/18] tracing/remotes: Add poll_ms " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 16/18] tracing/remotes: Add trace_remote cmdline options Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 17/18] Documentation: tracing/remotes: Add detailed tracefs layout Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 18/18] Documentation/kernel-parameters: Add trace_remote Vincent Donnefort
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260721103603.342266-4-vdonnefort@google.com \
--to=vdonnefort@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox