linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH] tracing: Fix to avoid wakeup loop in splice read of per-cpu buffer
Date: Mon, 21 Aug 2023 23:19:18 +0900	[thread overview]
Message-ID: <169262755804.106231.8245792908363050528.stgit@devnote2> (raw)

From: Masami Hiramatsu (Google) <mhiramat@kernel.org>

ftrace user can set 0 or small number to the 'buffer_percent' for quick
response for the ring buffer. In that case wait_on_pipe() will return
before filling a page of the ring buffer. That is too soon for splice()
because ring_buffer_read_page() will fail again.
This leads unnecessary loop in tracing_buffers_splice_read().

Set a minimum percentage of the buffer which is enough to fill a page to
wait_on_pipe() to avoid this situation.

Fixes: 03329f993978 ("tracing: Add tracefs file buffer_percentage")
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
---
 kernel/trace/trace.c |   12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index b8870078ef58..88448e8d8214 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -8462,6 +8462,8 @@ tracing_buffers_splice_read(struct file *file, loff_t *ppos,
 	/* did we read anything? */
 	if (!spd.nr_pages) {
 		long wait_index;
+		size_t nr_pages;
+		size_t full;
 
 		if (ret)
 			goto out;
@@ -8472,7 +8474,15 @@ tracing_buffers_splice_read(struct file *file, loff_t *ppos,
 
 		wait_index = READ_ONCE(iter->wait_index);
 
-		ret = wait_on_pipe(iter, iter->tr->buffer_percent);
+		/* For splice, we have to ensure at least 1 page is filled */
+		nr_pages = ring_buffer_nr_pages(iter->array_buffer->buffer, iter->cpu_file);
+		if (nr_pages * iter->tr->buffer_percent < 100) {
+			full = nr_pages + 99;
+			do_div(full, nr_pages);
+		} else
+			full = iter->tr->buffer_percent;
+
+		ret = wait_on_pipe(iter, full);
 		if (ret)
 			goto out;
 


             reply	other threads:[~2023-08-21 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 14:19 Masami Hiramatsu (Google) [this message]
2023-08-21 15:16 ` [PATCH] tracing: Fix to avoid wakeup loop in splice read of per-cpu buffer Masami Hiramatsu
2023-08-21 15:27   ` Steven Rostedt
2023-08-21 23:50     ` Masami Hiramatsu
2023-08-22  0:15 ` Masami Hiramatsu
2023-08-22  4:00 ` kernel test robot
2023-08-22  6:56 ` kernel test robot
2023-08-22  8:59 ` Steven Rostedt
2023-08-22 12:51   ` Masami Hiramatsu
2023-08-23 12:18 ` kernel test robot

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=169262755804.106231.8245792908363050528.stgit@devnote2 \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).