From: Dan Carpenter <dan.carpenter@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] tracing: off by one in __trace_array_vprintk()
Date: Wed, 26 Nov 2014 14:37:19 +0000 [thread overview]
Message-ID: <20141126143719.GT4893@mwanda> (raw)
In-Reply-To: <20141126092706.5d4038d4@gandalf.local.home>
On Wed, Nov 26, 2014 at 09:27:06AM -0500, Steven Rostedt wrote:
> On Wed, 26 Nov 2014 17:06:21 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > This check says "goto out;" if we had to truncate the string.
> >
> > The "tbuffer" buffer has TRACE_BUF_SIZE bytes. The vsnprintf() function
> > returns the number of characters (not counting the NUL char) which would
> > have been printed if there were space. If we we tried to print
> > TRACE_BUF_SIZE characters, the last character would have been truncated
> > to make space for the NUL character so we should "goto out;".
> >
>
> Oh, and the NUL character is never copied. We copy the string into the
> buffer with:
>
> memcpy(&entry->buf, tbuffer, len);
>
> Where len does not include NUL, and why we add it ourselves.
Yeah. I noticed that. Probably we should change the memcpy() to:
memcpy(&entry->buf, tbuffer, len + 1);
and remove separate NUL assignment? It's a speedup! I'll do it in v2.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] tracing: off by one in __trace_array_vprintk()
Date: Wed, 26 Nov 2014 17:37:19 +0300 [thread overview]
Message-ID: <20141126143719.GT4893@mwanda> (raw)
In-Reply-To: <20141126092706.5d4038d4@gandalf.local.home>
On Wed, Nov 26, 2014 at 09:27:06AM -0500, Steven Rostedt wrote:
> On Wed, 26 Nov 2014 17:06:21 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > This check says "goto out;" if we had to truncate the string.
> >
> > The "tbuffer" buffer has TRACE_BUF_SIZE bytes. The vsnprintf() function
> > returns the number of characters (not counting the NUL char) which would
> > have been printed if there were space. If we we tried to print
> > TRACE_BUF_SIZE characters, the last character would have been truncated
> > to make space for the NUL character so we should "goto out;".
> >
>
> Oh, and the NUL character is never copied. We copy the string into the
> buffer with:
>
> memcpy(&entry->buf, tbuffer, len);
>
> Where len does not include NUL, and why we add it ourselves.
Yeah. I noticed that. Probably we should change the memcpy() to:
memcpy(&entry->buf, tbuffer, len + 1);
and remove separate NUL assignment? It's a speedup! I'll do it in v2.
regards,
dan carpenter
next prev parent reply other threads:[~2014-11-26 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 14:06 [patch] tracing: off by one in __trace_array_vprintk() Dan Carpenter
2014-11-26 14:06 ` Dan Carpenter
2014-11-26 14:25 ` Steven Rostedt
2014-11-26 14:25 ` Steven Rostedt
2014-11-26 14:34 ` Dan Carpenter
2014-11-26 14:34 ` Dan Carpenter
2014-11-26 14:27 ` Steven Rostedt
2014-11-26 14:27 ` Steven Rostedt
2014-11-26 14:37 ` Dan Carpenter [this message]
2014-11-26 14:37 ` Dan Carpenter
2014-11-26 14:43 ` Steven Rostedt
2014-11-26 14:43 ` Steven Rostedt
2014-11-26 15:05 ` Dan Carpenter
2014-11-26 15:05 ` Dan Carpenter
2014-11-26 15:22 ` Steven Rostedt
2014-11-26 15:22 ` Steven Rostedt
2014-11-26 15:46 ` Dan Carpenter
2014-11-26 15:46 ` Dan Carpenter
2014-11-27 15:57 ` [patch v2] tracing: truncated output is better than nothing Dan Carpenter
2014-11-27 15:57 ` Dan Carpenter
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=20141126143719.GT4893@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.