From: Rabin Vincent <rabin@rab.in>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WARNING at __ftrace_hash_rec_update()
Date: Fri, 11 Nov 2011 15:44:19 +0530 [thread overview]
Message-ID: <20111111101419.GA4603@debian> (raw)
In-Reply-To: <1320453094.26400.0.camel@gandalf.stny.rr.com>
On Fri, Nov 04, 2011 at 08:31:34PM -0400, Steven Rostedt wrote:
> On Tue, 2011-11-01 at 19:45 +0530, Rabin Vincent wrote:
> > On v3.1-7810-g094803e (current linus git), I'm able to trigger the below
> > FTRACE_WARN_ON() by running the following sequence of commands.
> > DYNAMIC_FTRACE is enabled.
> >
> > ftrace.c:1384:
> > if (FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0))
> > return;
> > rec->flags--;
> >
>
> Thanks for reporting. Can you try this patch please.
Works for me, thanks. It needed a ret=0 which I see you've already
added in your official submission.
next prev parent reply other threads:[~2011-11-11 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 14:15 WARNING at __ftrace_hash_rec_update() Rabin Vincent
2011-11-05 0:31 ` Steven Rostedt
2011-11-11 10:14 ` Rabin Vincent [this message]
2011-11-18 23:14 ` [tip:perf/core] ftrace: Fix hash record accounting bug tip-bot for Steven Rostedt
2011-12-06 6:29 ` tip-bot for Steven Rostedt
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=20111111101419.GA4603@debian \
--to=rabin@rab.in \
--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