From: Harvey Harrison <harvey.harrison@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>
Subject: Re: [patch] clean hex output of ftrace
Date: Thu, 09 Oct 2008 16:53:46 -0700 [thread overview]
Message-ID: <1223596426.17735.0.camel@brick> (raw)
In-Reply-To: <20081009123113.GB2952@elte.hu>
On Thu, 2008-10-09 at 14:31 +0200, Ingo Molnar wrote:
> * Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
> > On Wed, 2008-10-08 at 17:16 -0700, Joe Perches wrote:
> > > On Wed, 8 Oct 2008, Harvey Harrison wrote:
> > > > From: Harvey Harrison <harvey.harrison@gmail.com>
> > > > Subject: [PATCH] ftrace: Fix inversion of hex output and use common routines
> > >
> > > You're quick...
> > >
> > > > BUG_ON(len >= HEX_CHARS);
> > >
> > > I think the BUG_ON is senseless.
> > >
> >
> > Agreed, it probably meant to say BUG_ON(len * 2 > HEX_CHARS -1)
> >
> > But as this is only called from within a helper macro, it could be
> > changed to a build-time check instead of a runtime:
> >
> > From: Harvey Harrison <harvey.harrison@gmail.com>
> > Subject: [PATCH] trace: add build-time check to avoid overrunning hex buffer
>
> applied to tip/tracing/core:
>
> bb86ba7: trace: add build-time check to avoid overrunning hex buffer
> 32ce86f: ftrace: fix hex output mode of ftrace
>
Thinking about this, these should probably be forwarded to -stable once
they go into mainline.
Cheers,
Harvey
next prev parent reply other threads:[~2008-10-09 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.30.0810081715520.2487-100000@perches.com>
2008-10-09 0:44 ` [patch] clean hex output of ftrace Harvey Harrison
2008-10-09 12:31 ` Ingo Molnar
2008-10-09 23:53 ` Harvey Harrison [this message]
2008-10-08 22:04 trem
2008-10-08 22:22 ` Joe Perches
2008-10-08 23:51 ` Harvey Harrison
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=1223596426.17735.0.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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