All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: kvm-ppc@vger.kernel.org
Subject: [GIT PULL] Please pull my kvm-ppc-fixes-4.19-3 tag
Date: Fri, 05 Oct 2018 00:29:43 +0000	[thread overview]
Message-ID: <20181005002943.GA18101@fergus> (raw)
In-Reply-To: <20180303091717.GA14569@fergus.ozlabs.ibm.com>

Paolo or Radim,

Please do a pull from my kvm-ppc-fixes-4.19-3 tag to get one commit
that fixes a host crash that I have seen when a page fault on a radix
guest on POWER9 happens concurrently with a THP collapse operation.
The bug is only in 4.19-rc and hence the fix does not need to be
backported to any stable kernel tree.

Thanks,
Paul.

The following changes since commit 71d29f43b6332badc5598c656616a62575e83342:

  KVM: PPC: Book3S HV: Don't use compound_order to determine host mapping size (2018-09-12 08:50:50 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-fixes-4.19-3

for you to fetch changes up to 6579804c431712d56956a63b1a01509441cc6800:

  KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix page fault (2018-10-04 14:51:11 +1000)

----------------------------------------------------------------
Third set of PPC KVM fixes for 4.19

One patch here, fixing a potential host crash introduced (or at least
exacerbated) by a previous fix for corruption relating to radix guest
page faults and THP operations.

----------------------------------------------------------------
Paul Mackerras (1):
      KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix page fault

 arch/powerpc/kvm/book3s_64_mmu_radix.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

  parent reply	other threads:[~2018-10-05  0:29 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  9:17 [GIT PULL] Please pull my kvm-ppc-fixes-4.16-1 tag Paul Mackerras
2018-03-06 17:08 ` Radim Krčmář
2018-03-14  8:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-2 tag Paul Mackerras
2018-03-15 20:57 ` Paolo Bonzini
2018-03-23  4:46 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-3 tag Paul Mackerras
2018-03-23 17:21 ` Paolo Bonzini
2018-05-24  5:34 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.17-1 tag Paul Mackerras
2018-05-24 17:02 ` Radim Krčmář
2018-08-22 12:08 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-1 tag Paul Mackerras
2018-09-14  9:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-2 tag Paul Mackerras
2018-09-18 13:22 ` Paolo Bonzini
2018-10-05  0:29 ` Paul Mackerras [this message]
2018-10-05  7:43 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-3 tag Paolo Bonzini
2018-11-16 10:36 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.20-1 tag Paul Mackerras
2018-11-25 17:54 ` Paolo Bonzini
2019-04-07 22:12 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.1-1 tag Paul Mackerras
2019-04-07 22:12   ` Paul Mackerras
2019-04-18  4:05   ` Paul Mackerras
2019-04-18  4:05     ` Paul Mackerras
2019-04-18 16:53     ` Paolo Bonzini
2019-04-18 16:53       ` Paolo Bonzini
2019-05-30 11:59 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.2-1 tag Paul Mackerras
2019-05-30 11:59   ` Paul Mackerras
2019-05-31 22:48   ` Paolo Bonzini
2019-05-31 22:48     ` Paolo Bonzini
2019-08-27  9:53 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag Paul Mackerras
2019-08-27  9:53   ` Paul Mackerras
2019-08-27 15:49   ` Radim Krčmář
2019-08-27 15:49     ` Radim Krčmář
2019-10-21  4:19 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.4-1 tag Paul Mackerras
2019-10-21  4:19   ` Paul Mackerras
2019-10-22 11:12   ` Paolo Bonzini
2019-10-22 11:12     ` Paolo Bonzini
2019-12-19  0:19 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.5-1 tag Paul Mackerras
2019-12-19  0:19   ` Paul Mackerras
2019-12-22 12:18   ` Paolo Bonzini
2019-12-22 12:18     ` Paolo Bonzini
2020-04-20 23:53 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.7-1 tag Paul Mackerras
2020-04-20 23:53   ` Paul Mackerras
2020-04-21 13:37   ` Paolo Bonzini
2020-04-21 13:37     ` Paolo Bonzini

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=20181005002943.GA18101@fergus \
    --to=paulus@ozlabs.org \
    --cc=kvm-ppc@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.