From: Frederic Weisbecker <fweisbec@gmail.com>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, tglx@linutronix.de, daniel@caiaq.de,
mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/ftrace] kernel/trace/trace_functions_graph.c: fix nsecs_str buffer size
Date: Mon, 23 Mar 2009 17:47:46 +0100 [thread overview]
Message-ID: <20090323164745.GB5988@nowhere> (raw)
In-Reply-To: <tip-603b9b9081ae0a1af986b9059a0a5055876ddea9@git.kernel.org>
On Mon, Mar 23, 2009 at 04:42:27PM +0000, Daniel Mack wrote:
> Commit-ID: 603b9b9081ae0a1af986b9059a0a5055876ddea9
> Gitweb: http://git.kernel.org/tip/603b9b9081ae0a1af986b9059a0a5055876ddea9
> Author: Daniel Mack <daniel@caiaq.de>
> AuthorDate: Mon, 23 Mar 2009 17:10:37 +0100
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Mon, 23 Mar 2009 17:40:51 +0100
>
> kernel/trace/trace_functions_graph.c: fix nsecs_str buffer size
>
> Impact: fix currently inactive buffer-overflow
>
> In kernel/trace/trace_functions_graph.c, print_graph_duration(),
> len can be as low as 1 or 2, which could make snprintf() write
> beyond the buffer bounds. (Found by cppcheck, no real-world bug
> occured)
>
> Signed-off-by: Daniel Mack <daniel@caiaq.de>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> LKML-Reference: <1237824637-28190-1-git-send-email-daniel@caiaq.de>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
>
> ---
> kernel/trace/trace_functions_graph.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Ingo, as I explained to Daniel before (I should have Cc you),
there is no overflow to protect here, so this patch will not
change anything.
This is my bad, I should better comment my code.
Frederic.
> diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c
> index e876816..a305472 100644
> --- a/kernel/trace/trace_functions_graph.c
> +++ b/kernel/trace/trace_functions_graph.c
> @@ -430,7 +430,7 @@ print_graph_duration(unsigned long long duration, struct trace_seq *s)
> unsigned long nsecs_rem = do_div(duration, 1000);
> /* log10(ULONG_MAX) + '\0' */
> char msecs_str[21];
> - char nsecs_str[5];
> + char nsecs_str[8];
> int ret, len;
> int i;
>
next prev parent reply other threads:[~2009-03-23 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 16:10 [PATCH] kernel/trace/trace_functions_graph.c: fix nsecs_str buffer size Daniel Mack
2009-03-23 16:40 ` Frederic Weisbecker
2009-03-23 16:57 ` Daniel Mack
2009-03-23 16:42 ` [tip:tracing/ftrace] " Daniel Mack
2009-03-23 16:47 ` Frederic Weisbecker [this message]
2009-03-23 17:15 ` 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=20090323164745.GB5988@nowhere \
--to=fweisbec@gmail.com \
--cc=daniel@caiaq.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.