Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751274AbdHXHxZ (ORCPT ); Thu, 24 Aug 2017 03:53:25 -0400 Received: from mail-wr0-f196.google.com ([209.85.128.196]:35626 "EHLO mail-wr0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751135AbdHXHxY (ORCPT ); Thu, 24 Aug 2017 03:53:24 -0400 Date: Thu, 24 Aug 2017 09:53:20 +0200 From: Ingo Molnar To: Jeffrey Hugo Cc: "Paul E. McKenney" , tglx@linutronix.de, bigeasy@linutronix.de, anna-maria@linutronix.de, boris.ostrovsky@oracle.com, richard@nod.at, linux-kernel@vger.kernel.org Subject: Re: [RFC GIT PULL rcu/next] RCU/hotplug fix Message-ID: <20170824075320.rqyfph3wcmnqzga2@gmail.com> References: <20170728003547.GA10932@linux.vnet.ibm.com> <20170815084324.k7ixgfjzqdu5kzhm@gmail.com> <68a1c2b3-d23b-a1e7-b0f7-a182e6b170d1@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <68a1c2b3-d23b-a1e7-b0f7-a182e6b170d1@codeaurora.org> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1367 Lines: 41 * Jeffrey Hugo wrote: > > > This commit has been exposed to 0day test robot and -next testing > > > and is available in the git repository at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo > > > > > > for you to fetch changes up to a58163d8ca2c8d288ee9f95989712f98473a5ac2: > > > > > > rcu: Migrate callbacks earlier in the CPU-offline timeline (2017-07-25 13:03:43 -0700) > > > > > > ---------------------------------------------------------------- > > > Paul E. McKenney (1): > > > rcu: Migrate callbacks earlier in the CPU-offline timeline > > > > > > include/linux/rcupdate.h | 1 + > > > kernel/cpu.c | 1 + > > > kernel/rcu/tree.c | 209 +++++++++++++++++++++++++---------------------- > > > 3 files changed, 115 insertions(+), 96 deletions(-) > > > > Pulled, thanks Paul! > > > > Ingo > > > > Ingo, > > We've been keeping an eye on this fix, so I'm trying to ascertain it's status. > For my information, is this expected to hit Linus' tree in 4.13, or wait until > the 4.14 merge window? It's for v4.14, it's a pretty large (and thus risky) commit that came in relatively late. If it's problem-free it can be sent to -stable. If Paul insists I can try and send it to Linus, but it's getting fairly late in the cycle. Thanks, Ingo