From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH 2/4] [PATCH 2/4] tracing: fix trace_seq_printf return value
Date: Fri, 23 Oct 2009 19:36:17 -0400 [thread overview]
Message-ID: <20091023233646.631787612@goodmis.org> (raw)
In-Reply-To: <20091023233615.661789185@goodmis.org>
[-- Attachment #1: 0002-tracing-fix-trace_seq_printf-return-value.patch --]
[-- Type: text/plain, Size: 1667 bytes --]
From: Jiri Olsa <jolsa@redhat.com>
trace_seq_printf return value is a little ambiguous. It currently
returns the length of the space available in the buffer. printf
usually returns the amount written. This is not adequate here, because
trace_seq_printf(s, "");
is perfectly legal, and returning 0 would indicate that it failed.
We can always see the amount written by looking at the before and after
values of s->len. This is not quite the same use as printf. We only care
if the string was successfully written to the buffer or not.
Making trace_seq_printf return 0 if the trace oversizes the buffer's free
space, 1 otherwise.
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
LKML-Reference: <20091022120958.GB2311@jolsa.redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/trace_output.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/kernel/trace/trace_output.c b/kernel/trace/trace_output.c
index ed17565..b6c12c6 100644
--- a/kernel/trace/trace_output.c
+++ b/kernel/trace/trace_output.c
@@ -69,6 +69,9 @@ enum print_line_t trace_print_printk_msg_only(struct trace_iterator *iter)
* @s: trace sequence descriptor
* @fmt: printf format string
*
+ * It returns 0 if the trace oversizes the buffer's free
+ * space, 1 otherwise.
+ *
* The tracer may use either sequence operations or its own
* copy to user routines. To simplify formating of a trace
* trace_seq_printf is used to store strings into a special
@@ -95,7 +98,7 @@ trace_seq_printf(struct trace_seq *s, const char *fmt, ...)
s->len += ret;
- return len;
+ return 1;
}
EXPORT_SYMBOL_GPL(trace_seq_printf);
--
1.6.3.3
next prev parent reply other threads:[~2009-10-23 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:36 [PATCH 0/4] [GIT PULL] tracing: various fixes Steven Rostedt
2009-10-23 23:36 ` [PATCH 1/4] [PATCH 1/4] tracing: updating *ppos instead of filp->f_pos Steven Rostedt
2009-10-23 23:36 ` Steven Rostedt [this message]
2009-10-23 23:36 ` [PATCH 3/4] [PATCH 3/4] tracing: comment typo and documentation example fix Steven Rostedt
2009-10-23 23:36 ` [PATCH 4/4] [PATCH 4/4] tracing: removing cpu arg from rb_time_stamp function Steven Rostedt
2009-10-24 9:08 ` [PATCH 0/4] [GIT PULL] tracing: various fixes Ingo Molnar
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=20091023233646.631787612@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome