All of lore.kernel.org
 help / color / mirror / Atom feed
From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-riscv@lists.infradead.org
Subject: Unable to handle kernel paging request at virtual address 0000001bf8068693
Date: Wed, 5 Sep 2018 14:07:08 -0700	[thread overview]
Message-ID: <20180905210708.GC4225@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180905190648.GC1420@infradead.org>

On Wed, Sep 05, 2018 at 12:06:48PM -0700, Christoph Hellwig wrote:
> On Wed, Sep 05, 2018 at 10:17:08AM -0700, Atish Patra wrote:
> > This issue is fixed in 4.19-rc1.
> > 
> > If you don't want to pull the latest, here is the change you need to
> > cherry-pick to your branch.
> > 
> > https://lore.kernel.org/lkml/20180626192746.GJ3593 at linux.vnet.ibm.com/
> 
> Paul, I think we need this in 4.18-stable.
> 
> Also Palmer, I think we should pick it up in riscv-linux-4.18.
> 
> The mainline commit is:
> 
> commit fcc63543650150629c8a873cbef3578770acecd9
> Author: Boqun Feng <boqun.feng@gmail.com>
> Date:   Fri Jun 15 12:06:31 2018 -0700
> 
>     rcu: Make expedited GPs handle CPU 0 being offline

OK, it backports cleanly and passes a short rcutorture test.  You guys
have tested it, correct?  If so, I am happy to pass it on to -stable.

							Thanx, Paul

  reply	other threads:[~2018-09-05 21:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 13:29 Unable to handle kernel paging request at virtual address 0000001bf8068693 Andreas Schwab
2018-09-05 17:17 ` Atish Patra
2018-09-05 19:06   ` Christoph Hellwig
2018-09-05 21:07     ` Paul E. McKenney [this message]
2018-09-06  4:10       ` Atish Patra
2018-09-06  4:20         ` Paul E. McKenney
2018-09-07  0:24           ` Atish Patra
2018-09-07  3:45             ` Paul E. McKenney
2018-09-06  7:35     ` Andreas Schwab
2018-09-06 17:50       ` Paul E. McKenney
2018-09-18 22:53     ` Palmer Dabbelt
  -- strict thread matches above, loose matches on Subject: below --
2018-09-05 13:25 Andreas Schwab
2018-09-05 12:58 Andreas Schwab

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=20180905210708.GC4225@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-riscv@lists.infradead.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.