All of lore.kernel.org
 help / color / mirror / Atom feed
From: paulmck@linux.ibm.com (Paul E. McKenney)
Subject: v5.0-rc2 and NVMeOF
Date: Wed, 27 Feb 2019 10:22:29 -0800	[thread overview]
Message-ID: <20190227182229.GH4072@linux.ibm.com> (raw)
In-Reply-To: <1551284750.31902.196.camel@acm.org>

On Wed, Feb 27, 2019@08:25:50AM -0800, Bart Van Assche wrote:
> On Wed, 2019-02-27@08:04 -0800, Paul E. McKenney wrote:
> > On Tue, Feb 26, 2019@03:48:07PM -0800, Bart Van Assche wrote:
> > > On Tue, 2019-02-26@11:20 -0800, Paul E. McKenney wrote:
> > > > On Tue, Feb 26, 2019@10:40:03AM -0800, Bart Van Assche wrote:
> > > > > On Tue, 2019-02-26@10:12 -0800, Paul E. McKenney wrote:
> > > > > > But if you want me to try to push this into v5.1, I need you to very
> > > > > > explicitly tell me that you want me to do this.  Sorry to be picky, but
> > > > > > my normal process cut off contributions to v5.0 more than a month ago,
> > > > > > and my usual position is that a backport to -stable covers almost all
> > > > > > use cases and reduces risk to those using mainline.  Yes, RCU patches
> > > > > > do start off under a considerable cloud of suspicion.  Which is one of
> > > > > > the reasons that RCU works at all.  ;-)
> > > > > > 
> > > > > > So again, if you need me to try to push this into v5.1, I do need an
> > > > > > explicit request from you.
> > > > > 
> > > > > Hi Paul,
> > > > > 
> > > > > If this patch will only be sent to Linus during the v5.2 merge window, will
> > > > > a "Cc: stable # v..." tag be added to this patch that causes this patch to
> > > > > be applied to kernel versions before v5.2 on which it is safe to apply this
> > > > > patch?
> > > > 
> > > > I would prefer that, especially if you let me know which versions that
> > > > are important to you.  ;-)
> > > 
> > > Hi Paul,
> > > 
> > > Is this the commit that introduced WQ_MEM_RECLAIM queues for SRCU?
> > > 
> > > ad7c946b35ad ("rcu: Create RCU-specific workqueues with rescuers") # v4.17
> > > 
> > > Since the commit earlier in this e-mail thread reverts changes introduced in
> > > kernel v4.18 I propose to request the stable tree maintainers to backport
> > > this patch to the v4.18 and later stable kernel trees.
> > 
> > That is the one!  Hmmm...  Looks like these have to be backported by hand.
> > Or am I just confused this morning?
> 
> Hi Paul,
> 
> In my e-mail I was referring to sending only commit c0bd8bc59c77 ("srcu: Remove
> cleanup_srcu_struct_quiesced()") to the stable kernel tree maintainers. Are you
> perhaps referring to another commit?

Hello, Bart,

I am not having much luck automatically applying either of those two
commits.  Perhaps pilot error.  Does it work for you?

Ah, I back-ported that patch for you, didn't I?  If so would you be willing
to take care of sending it to -stable once c0bd8bc59c77 ("srcu: Remove
cleanup_srcu_struct_quiesced()") hits mainline?

							Thanx, Paul

  reply	other threads:[~2019-02-27 18:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 19:07 v5.0-rc2 and NVMeOF Bart Van Assche
2019-01-17  1:16 ` Sagi Grimberg
2019-02-11 17:24   ` Bart Van Assche
2019-02-11 21:08     ` Paul E. McKenney
2019-02-11 22:27       ` Bart Van Assche
2019-02-12  1:24         ` Paul E. McKenney
2019-02-12 16:47           ` Bart Van Assche
2019-02-12 17:47             ` Paul E. McKenney
2019-02-12 19:15               ` Paul E. McKenney
2019-02-13  0:44                 ` Bart Van Assche
2019-02-13  1:10                   ` Paul E. McKenney
2019-02-13 15:19                     ` Paul E. McKenney
2019-02-13 15:24                       ` Paul E. McKenney
2019-02-13 18:36                         ` Bart Van Assche
2019-02-13 18:48                           ` Paul E. McKenney
2019-02-13 19:12                             ` Bart Van Assche
2019-02-13 19:30                               ` Paul E. McKenney
2019-02-13 19:52                                 ` Paul E. McKenney
2019-02-13 21:00                                   ` Bart Van Assche
2019-02-13 22:09                                     ` Paul E. McKenney
2019-02-13 23:07                                       ` Paul E. McKenney
2019-02-14  0:21                                       ` Bart Van Assche
2019-02-14  1:02                                         ` Paul E. McKenney
2019-02-26 17:35                                           ` Paul E. McKenney
2019-02-26 17:47                                             ` Bart Van Assche
2019-02-26 18:12                                               ` Paul E. McKenney
2019-02-26 18:40                                                 ` Bart Van Assche
2019-02-26 19:20                                                   ` Paul E. McKenney
2019-02-26 23:48                                                     ` Bart Van Assche
2019-02-27 16:04                                                       ` Paul E. McKenney
2019-02-27 16:25                                                         ` Bart Van Assche
2019-02-27 18:22                                                           ` Paul E. McKenney [this message]
2019-02-13 19:13                         ` Paul E. McKenney
2019-02-13  0:47               ` Bart Van Assche
2019-02-13  1:07                 ` Paul E. McKenney

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=20190227182229.GH4072@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    /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.