All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: <gregkh@linuxfoundation.org>
Cc: mathieu.desnoyers@efficios.com, akpm@linux-foundation.org,
	metze@samba.org, mingo@redhat.com, paulmck@kernel.org,
	peterz@infradead.org, <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] tracepoint: Use rcu get state and cond sync for static call" failed to apply to 5.10-stable tree
Date: Thu, 19 Aug 2021 17:09:33 -0400	[thread overview]
Message-ID: <20210819170933.5c4c6a38@oasis.local.home> (raw)
In-Reply-To: <1628500832155134@kroah.com>

On Mon, 09 Aug 2021 11:20:32 +0200
<gregkh@linuxfoundation.org> wrote:

> The patch below does not apply to the 5.10-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>.
> 

Crap.

Mathieu, seems that the "slow down 10x" patch was able to be backported
to 5.10, where as this patch was not. Reason being is that
start_poll_synchronize_rcu() was added in 5.13.

This means because the other patch was able to be backported without
this patch, we just slowed down disabling all events! Which may be a
surprise to some people not expecting a stable branch from having such
a big performance regression :-/

-- Steve

  reply	other threads:[~2021-08-19 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09  9:20 FAILED: patch "[PATCH] tracepoint: Use rcu get state and cond sync for static call" failed to apply to 5.10-stable tree gregkh
2021-08-19 21:09 ` Steven Rostedt [this message]
2021-08-20  0:42   ` Steven Rostedt
2021-08-20 16:34     ` Steven Rostedt
2021-08-20 17:25     ` Mathieu Desnoyers
2021-08-20 17:57     ` Paul E. McKenney
2021-08-20 22:13       ` Steven Rostedt
2021-09-01  9:24         ` Greg KH

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=20210819170933.5c4c6a38@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=metze@samba.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.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 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.