public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Paolo Bonzini" <pbonzini@redhat•com>,
	"Radim Krčmář" <rkrcmar@redhat•com>, KVM <kvm@vger•kernel.org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Marios Pomonis <pomonis@google•com>, Nick Finco <nifi@google•com>
Subject: linux-next: Fixes tags need some work in the kvm tree
Date: Fri, 24 Jan 2020 14:22:55 +1100	[thread overview]
Message-ID: <20200124142255.3f4f2e5e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2812 bytes --]

Hi all,

In commit

  99a88de84ef9 ("KVM: x86: Protect pmu_intel.c from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 25462f7f5295 ("KVM: x86/vPMU: Define kvm_pmu_ops to support vPMU function dispatch")

In commit

  fdf9f340769d ("KVM: x86: Protect DR-based index computations from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 020df0794f57 ("KVM: move DR register access handling into generic code")

In commit

  649ea1dce49d ("KVM: x86: Protect exit_reason from being used in Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 55d2375e58a6 ("KVM: nVMX: Move nested code to dedicated files")

In commit

  202276f43207 ("KVM: x86: Protect MSR-based index computations from Spectre-v1/L1TF attacks in x86.c")

Fixes tag

  Fixes: commit 890ca9aefa78 ("KVM: Add MCE support")

In commit

  5135ee39a7bf ("KVM: x86: Protect MSR-based index computations in pmu.h from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 25462f7f5295 ("KVM: x86/vPMU: Define kvm_pmu_ops to support vPMU function dispatch")

In commit

  fa8c3fb1c109 ("KVM: x86: Protect MSR-based index computations in fixed_msr_to_seg_unit() from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit de9aef5e1ad6 ("KVM: MTRR: introduce fixed_mtrr_segment table")

In commit

  6c7fe168f928 ("KVM: x86: Protect kvm_lapic_reg_write() from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 0105d1a52640 ("KVM: x2apic interface to lapic")

In commit

  c895c1d45f4f ("KVM: x86: Protect ioapic_write_indirect() from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 70f93dae32ac ("KVM: Use temporary variable to shorten lines.")

In commit

  8174f8bb6866 ("KVM: x86: Protect ioapic_read_indirect() from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit a2c118bfab8b ("KVM: Fix bounds checking in ioapic indirect register reads (CVE-2013-1798)")

In commit

  b685a30c564c ("KVM: x86: Refactor picdev_write() to prevent Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 85f455f7ddbe ("KVM: Add support for in-kernel PIC emulation")

In commit

  f54ae8da934e ("KVM: x86: Protect kvm_hv_msr_[get|set]_crash_data() from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit e7d9513b60e8 ("kvm/x86: added hyper-v crash msrs into kvm hyperv context")

In commit

  f4ff5079e328 ("KVM: x86: Protect x86_decode_insn from Spectre-v1/L1TF attacks")

Fixes tag

  Fixes: commit 045a282ca415 ("KVM: emulator: implement fninit, fnstsw, fnstcw")

In all these, the leading work 'commit' is unexpected.  The fixes tag
can be gernerated using

	git log -1 --format='Fixes: %h ("%s")' <fixed commit>

Also, please keep all the commit message tags together at the end of
the commit message.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2020-01-24  3:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24  3:22 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-03 21:49 linux-next: Fixes tags need some work in the kvm tree Stephen Rothwell

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=20200124142255.3f4f2e5e@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=nifi@google$(echo .)com \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=pomonis@google$(echo .)com \
    --cc=rkrcmar@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox