From: Shawn Bohrer <shawn.bohrer@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: old version of trace-cmd broken on 3.10 kernel
Date: Fri, 31 May 2013 12:10:07 -0500 [thread overview]
Message-ID: <20130531171007.GD2910@sbohrermbp13-local.rgmadvisors.com> (raw)
In-Reply-To: <1370019935.26799.53.camel@gandalf.local.home>
On Fri, May 31, 2013 at 01:05:35PM -0400, Steven Rostedt wrote:
> On Fri, 2013-05-31 at 11:50 -0500, Shawn Bohrer wrote:
> > Not sure if this is a big deal or not. I've got an old version of
> > trace-cmd. It was built from git on 2012-09-12 but sadly I didn't
> > stash away the exact commit hash. Anyway this version works fine on a
> > 3.4 kernel but on a 3.10-rc3 kernel it no longer works. I just pulled
> > the latest trace-cmd from git and it works fine on the 3.10 kernel so
> > maybe this isn't an issue, but I don't typically expect applications
> > to break with a kernel upgrade.
> >
> > When I run the old version on 3.10.0-rc3 I get the following output:
>
> Yep, in 3.10 I fixed a long standing bug in the splice code, that when
> fixed, the old trace-cmd would fail.
>
> I made a fix to all the stable releases of trace-cmd and posted it to
> LKML back on March 1st.
>
> https://lkml.org/lkml/2013/3/1/596
Thanks Steve,
I'll just update my trace-cmd version. It is about time for an update
anyway.
Thanks,
Shawn
prev parent reply other threads:[~2013-05-31 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 16:50 Shawn Bohrer
2013-05-31 17:05 ` Steven Rostedt
2013-05-31 17:10 ` Shawn Bohrer [this message]
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=20130531171007.GD2910@sbohrermbp13-local.rgmadvisors.com \
--to=shawn.bohrer@gmail.com \
--cc=linux-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
all inboxes | Powered by JetHome®