diff options
| author | Mike Waychison <mikew@google.com> | 2011-06-03 13:04:53 -0700 |
|---|---|---|
| committer | Avi Kivity <avi@redhat.com> | 2011-06-06 11:27:52 +0300 |
| commit | 74b5c5bfff429f464c38dd49af41d75cf0e7dc26 (patch) | |
| tree | f191213a9807e88ca24c2aaf123734892fe9e792 /arch/x86 | |
| parent | 221192bdff2583834984639121595fc9296120d3 (diff) | |
| download | linux-3.10-74b5c5bfff429f464c38dd49af41d75cf0e7dc26.tar.gz linux-3.10-74b5c5bfff429f464c38dd49af41d75cf0e7dc26.tar.bz2 linux-3.10-74b5c5bfff429f464c38dd49af41d75cf0e7dc26.zip | |
KVM: Initialize kvm before registering the mmu notifier
It doesn't make sense to ever see a half-initialized kvm structure on
mmu notifier callbacks. Previously, 85722cda changed the ordering to
ensure that the mmu_lock was initialized before mmu notifier
registration, but there is still a race where the mmu notifier could
come in and try accessing other portions of struct kvm before they are
intialized.
Solve this by moving the mmu notifier registration to occur after the
structure is completely initialized.
Google-Bug-Id: 452199
Signed-off-by: Mike Waychison <mikew@google.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'arch/x86')
0 files changed, 0 insertions, 0 deletions