diff options
| author | Maxim Levitsky <mlevitsk@redhat.com> | 2022-02-07 17:54:19 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-02-08 13:30:47 -0500 |
| commit | e1779c2714c3023e4629825762bcbc43a3b943df (patch) | |
| tree | 0e8ffff7fe123b8e318e7427d4e3d98d79ce7fb2 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | c53bbe2145f51d3bc0438c2db02e737b9b598bf3 (diff) | |
KVM: x86: nSVM: fix potential NULL derefernce on nested migration
Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.
KVM can't even access guest memory at that point as nested NPT
is needed for that, and of course it won't initialize the walk_mmu,
which is main issue the patch was addressing.
Fix this for real.
Fixes: 232f75d3b4b5 ("KVM: nSVM: call nested_svm_load_cr3 on nested state load")
Cc: stable@vger.kernel.org
Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
Message-Id: <20220207155447.840194-3-mlevitsk@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions