diff options
| author | Jan Kiszka <jan.kiszka@siemens.com> | 2011-12-14 22:25:13 +0400 |
|---|---|---|
| committer | Paul Gortmaker <paul.gortmaker@windriver.com> | 2013-01-17 01:45:07 +0400 |
| commit | 9cb08e9f1df7113af1cf28534d73ef3adb419017 (patch) | |
| tree | cda057b9d99a61ef2e74287cbac4215789b2166c /include | |
| parent | 9b970b952ca4c0294a1fa0031ffaffeef23593ab (diff) | |
| download | linux-9cb08e9f1df7113af1cf28534d73ef3adb419017.tar.xz | |
KVM: x86: Prevent starting PIT timers in the absence of irqchip support
commit 0924ab2cfa98b1ece26c033d696651fd62896c69 upstream.
User space may create the PIT and forgets about setting up the irqchips.
In that case, firing PIT IRQs will crash the host:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000128
IP: [<ffffffffa10f6280>] kvm_set_irq+0x30/0x170 [kvm]
...
Call Trace:
[<ffffffffa11228c1>] pit_do_work+0x51/0xd0 [kvm]
[<ffffffff81071431>] process_one_work+0x111/0x4d0
[<ffffffff81071bb2>] worker_thread+0x152/0x340
[<ffffffff81075c8e>] kthread+0x7e/0x90
[<ffffffff815a4474>] kernel_thread_helper+0x4/0x10
Prevent this by checking the irqchip mode before starting a timer. We
can't deny creating the PIT if the irqchips aren't set up yet as
current user land expects this order to work.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions