This patch was introduced to prevent the unloading of lpfc driver when
doing NVMe BFS booting. Broadcom has identified that this patch
introduces a bug that prevents unloading of lpfc driver in the non-BFS
case as well.
export_imc_mode_and_cmd() function which creates the debugfs interface
for imc-mode and imc-command, is invoked when each nest pmu units is
registered.
When the first nest pmu unit is registered, export_imc_mode_and_cmd()
creates 'imc' directory under `/debug/powerpc/`. In the subsequent
invocations debugfs_create_dir() function returns, since the directory
already exists.
The recent commit <c33d442328f55> (debugfs: make error message a bit
more verbose), throws a warning if we try to invoke
`debugfs_create_dir()` with an already existing directory name.
Address this warning by making the debugfs directory registration in
the opal_imc_counters_probe() function, i.e invoke
export_imc_mode_and_cmd() function from the probe function.
Signed-off-by: Anju T Sudhakar <email address hidden>
Tested-by: Nageswara R Sastry <email address hidden>
Signed-off-by: Michael Ellerman <email address hidden>
Link: https://<email address hidden>
(cherry picked from commit 48e626ac85b43cc589dd1b3b8004f7f85f03544d)
Signed-off-by: Frank Heimes <email address hidden>
Acked-by: Colin Ian King <email address hidden>
Signed-off-by: Seth Forshee <email address hidden>
UBUNTU: SAUCE: x86/KVM: Clean up host's steal time structure
CVE-2019-3016
Now that we are mapping kvm_steal_time from the guest directly we
don't need keep a copy of it in kvm_vcpu_arch.st. The same is true
for the stime field.
This is part of CVE-2019-3016.
Signed-off-by: Boris Ostrovsky <email address hidden>
Reviewed-by: Joao Martins <email address hidden>
Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>
Signed-off-by: Seth Forshee <email address hidden>
UBUNTU: SAUCE: x86/KVM: Make sure KVM_VCPU_FLUSH_TLB flag is not missed
CVE-2019-3016
There is a potential race in record_steal_time() between setting
host-local vcpu->arch.st.steal.preempted to zero (i.e. clearing
KVM_VCPU_PREEMPTED) and propagating this value to the guest with
kvm_write_guest_cached(). Between those two events the guest may
still see KVM_VCPU_PREEMPTED in its copy of kvm_steal_time, set
KVM_VCPU_FLUSH_TLB and assume that hypervisor will do the right
thing. Which it won't.
Instad of copying, we should map kvm_steal_time and that will
guarantee atomicity of accesses to @preempted.
This is part of CVE-2019-3016.
Signed-off-by: Boris Ostrovsky <email address hidden>
Reviewed-by: Joao Martins <email address hidden>
Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>
Signed-off-by: Seth Forshee <email address hidden>
