Revision 313f636d5c490c9741d3f750dc8da33029edbc6b authored by David Matlack on 09 March 2016, 00:19:44 UTC, committed by Paolo Bonzini on 09 March 2016, 10:54:14 UTC
When growing halt-polling, there is no check that the poll time exceeds
the limit. It's possible for vcpu->halt_poll_ns grow once past
halt_poll_ns, and stay there until a halt which takes longer than
vcpu->halt_poll_ns. For example, booting a Linux guest with
halt_poll_ns=11000:

 ... kvm:kvm_halt_poll_ns: vcpu 0: halt_poll_ns 0 (shrink 10000)
 ... kvm:kvm_halt_poll_ns: vcpu 0: halt_poll_ns 10000 (grow 0)
 ... kvm:kvm_halt_poll_ns: vcpu 0: halt_poll_ns 20000 (grow 10000)

Signed-off-by: David Matlack <dmatlack@google.com>
Fixes: aca6ff29c4063a8d467cdee241e6b3bf7dc4a171
Cc: stable@vger.kernel.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
1 parent 9522b37
History
File Mode Size
Kconfig -rw-r--r-- 1.7 KB
Makefile -rw-r--r-- 312 bytes
fmc-chardev.c -rw-r--r-- 4.1 KB
fmc-core.c -rw-r--r-- 7.0 KB
fmc-dump.c -rw-r--r-- 2.6 KB
fmc-fakedev.c -rw-r--r-- 10.5 KB
fmc-match.c -rw-r--r-- 3.1 KB
fmc-sdb.c -rw-r--r-- 7.3 KB
fmc-trivial.c -rw-r--r-- 2.4 KB
fmc-write-eeprom.c -rw-r--r-- 4.1 KB
fru-parse.c -rw-r--r-- 1.8 KB

back to top