From: Paul Mackerras <paulus@ozlabs.org> To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org Cc: kvm-ppc@vger.kernel.org, Alexander Graf <agraf@suse.com> Subject: [GIT PULL] Please pull host DOS fix for HV KVM for 4.8-rc1 Date: Sat, 30 Jul 2016 11:14:27 +1000 [thread overview] Message-ID: <20160730011427.GA3922@fergus.ozlabs.ibm.com> (raw) Paolo, Please do a pull from my kvm-ppc-next branch to get two commits which are the fix for CVE-2016-5412. I would like them to get into upstream v4.8-rc1 as they fix a denial-of-service vulnerability in HV KVM on POWER8 machines. They were in linux-next yesterday without causing any conflicts. Thanks, Paul. The following changes since commit 912902ce78b0d48f717f9128e61fb9bffbd65f86: Merge tag 'kvm-arm-for-4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into next (2016-07-22 20:27:26 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git kvm-ppc-next for you to fetch changes up to 93d17397e4e2182fdaad503e2f9da46202c0f1c3: KVM: PPC: Book3S HV: Save/restore TM state in H_CEDE (2016-07-28 16:10:07 +1000) ---------------------------------------------------------------- Paul Mackerras (2): KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures KVM: PPC: Book3S HV: Save/restore TM state in H_CEDE arch/powerpc/kvm/book3s_hv_rmhandlers.S | 462 +++++++++++++++++--------------- 1 file changed, 250 insertions(+), 212 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@ozlabs.org> To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org Cc: kvm-ppc@vger.kernel.org, Alexander Graf <agraf@suse.com> Subject: [GIT PULL] Please pull host DOS fix for HV KVM for 4.8-rc1 Date: Sat, 30 Jul 2016 01:14:27 +0000 [thread overview] Message-ID: <20160730011427.GA3922@fergus.ozlabs.ibm.com> (raw) Paolo, Please do a pull from my kvm-ppc-next branch to get two commits which are the fix for CVE-2016-5412. I would like them to get into upstream v4.8-rc1 as they fix a denial-of-service vulnerability in HV KVM on POWER8 machines. They were in linux-next yesterday without causing any conflicts. Thanks, Paul. The following changes since commit 912902ce78b0d48f717f9128e61fb9bffbd65f86: Merge tag 'kvm-arm-for-4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into next (2016-07-22 20:27:26 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git kvm-ppc-next for you to fetch changes up to 93d17397e4e2182fdaad503e2f9da46202c0f1c3: KVM: PPC: Book3S HV: Save/restore TM state in H_CEDE (2016-07-28 16:10:07 +1000) ---------------------------------------------------------------- Paul Mackerras (2): KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures KVM: PPC: Book3S HV: Save/restore TM state in H_CEDE arch/powerpc/kvm/book3s_hv_rmhandlers.S | 462 +++++++++++++++++--------------- 1 file changed, 250 insertions(+), 212 deletions(-)
next reply other threads:[~2016-07-30 1:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-07-30 1:14 Paul Mackerras [this message] 2016-07-30 1:14 ` [GIT PULL] Please pull host DOS fix for HV KVM for 4.8-rc1 Paul Mackerras 2016-08-01 13:03 ` Radim Krčmář 2016-08-01 13:03 ` Radim Krčmář
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=20160730011427.GA3922@fergus.ozlabs.ibm.com \ --to=paulus@ozlabs.org \ --cc=agraf@suse.com \ --cc=kvm-ppc@vger.kernel.org \ --cc=kvm@vger.kernel.org \ --cc=pbonzini@redhat.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: linkBe 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.