All of lore.kernel.org
 help / color / mirror / Atom feed
* linux-next: Fixes tags need some work in the kvm tree
@ 2019-07-03 21:49 Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2019-07-03 21:49 UTC (permalink / raw)
  To: Paolo Bonzini, Radim Krčmář, KVM
  Cc: Linux Next Mailing List, Linux Kernel Mailing List

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

Hi all,

In commit

  e8a70bd4e925 ("KVM: nVMX: allow setting the VMFUNC controls MSR")

Fixes tag

  Fixes: 27c42a1bb ("KVM: nVMX: Enable VMFUNC for the L1 hypervisor", 2017-08-03)

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").
  - The trailing date is unexpected.
    Just use
	git log -1 --format='Fixes: %h ("%s")'

In commit

  6defc591846d ("KVM: nVMX: include conditional controls in /dev/kvm KVM_GET_MSRS")

Fixes tag

  Fixes: 1389309c811 ("KVM: nVMX: expose VMX capabilities for nested hypervisors to userspace", 2018-02-26)

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").
  - The trailing date is unexpected.
    Just use
	git log -1 --format='Fixes: %h ("%s")'

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* linux-next: Fixes tags need some work in the kvm tree
@ 2020-01-24  3:22 Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2020-01-24  3:22 UTC (permalink / raw)
  To: Paolo Bonzini, Radim Krčmář, KVM
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Marios Pomonis, Nick Finco

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-01-24  3:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-03 21:49 linux-next: Fixes tags need some work in the kvm tree Stephen Rothwell
2020-01-24  3:22 Stephen Rothwell

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.