stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: namhyung@kernel.org, mhiramat@kernel.org, mingo@kernel.org,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ftrace: Fix function pid filter on instances" failed to apply to 4.4-stable tree
Date: Wed, 19 Apr 2017 15:07:30 +0200	[thread overview]
Message-ID: <20170419130730.GA28924@kroah.com> (raw)
In-Reply-To: <20170419090233.115efda8@gandalf.local.home>

On Wed, Apr 19, 2017 at 09:02:33AM -0400, Steven Rostedt wrote:
> On Wed, 19 Apr 2017 13:42:40 +0200
> <gregkh@linuxfoundation.org> wrote:
> 
> > The patch below does not apply to the 4.4-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> 
> [..]
> 
> > 
> > To fix it, use ftrace_clear_pids() to unregister the probe.  As
> > instance_rmdir() already updated ftrace codes, it can just free the
> > filter safely.
> > 
> > Link: http://lkml.kernel.org/r/20170417024430.21194-2-namhyung@kernel.org
> > 
> > Fixes: 0c8916c34203 ("tracing: Add rmdir to remove multibuffer instances")
> 
> Hmm, this is wrong. It should have been:
> 
> Fixes: 345ddcc882d8 ("ftrace: Have set_ftrace_pid use the bitmap like events do")
> 
> Which was added in 4.8.
> 
> I doesn't need to go back further than that. Thanks!

Ah, thanks for clearing that up, much appreciated.

greg k-h

      reply	other threads:[~2017-04-19 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 11:42 FAILED: patch "[PATCH] ftrace: Fix function pid filter on instances" failed to apply to 4.4-stable tree gregkh
2017-04-19 13:02 ` Steven Rostedt
2017-04-19 13:07   ` Greg KH [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=20170419130730.GA28924@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).