summary refs log tree commit diff
path: root/src/plugin/mod.rs
diff options
context:
space:
mode:
authorDmitry Torokhov <dtor@chromium.org>2018-02-21 10:21:56 -0800
committerchrome-bot <chrome-bot@chromium.org>2018-03-08 00:37:33 -0800
commit532a94c1c83c1f829a03e5c95ae584a57c0e86d5 (patch)
tree530ec3652f5fb3d139ac245d9b943862b4849e52 /src/plugin/mod.rs
parente423460238fe1cfb8853faef3b855f1ce53b756c (diff)
downloadcrosvm-532a94c1c83c1f829a03e5c95ae584a57c0e86d5.tar
crosvm-532a94c1c83c1f829a03e5c95ae584a57c0e86d5.tar.gz
crosvm-532a94c1c83c1f829a03e5c95ae584a57c0e86d5.tar.bz2
crosvm-532a94c1c83c1f829a03e5c95ae584a57c0e86d5.tar.lz
crosvm-532a94c1c83c1f829a03e5c95ae584a57c0e86d5.tar.xz
crosvm-532a94c1c83c1f829a03e5c95ae584a57c0e86d5.tar.zst
crosvm-532a94c1c83c1f829a03e5c95ae584a57c0e86d5.zip
Fix race between un-pausing vcpu and requesting vcpu pause
To ensure that we do not miss pause request sent while we were in paused
state, or were exiting paused state, let's start using
KVM_SET_SIGNAL_MASK. SIGRTMIN() + 0 signal will be blocked and thus is
not delivered, and it will only be checked when KVM_RUN is being
executed, reliably interrupting KVM_RUN.

TEST=cargo test --features plugin; cargo test -p kvm; ./build_test
BUG=chromium:800626

Change-Id: Iae67a411c23c2b14fbfcbc7d53d0bc86ec4b67d9
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/944850
Reviewed-by: Zach Reizner <zachr@chromium.org>
Diffstat (limited to 'src/plugin/mod.rs')
-rw-r--r--src/plugin/mod.rs18
1 files changed, 17 insertions, 1 deletions
diff --git a/src/plugin/mod.rs b/src/plugin/mod.rs
index 853b7e5..4528df8 100644
--- a/src/plugin/mod.rs
+++ b/src/plugin/mod.rs
@@ -26,7 +26,7 @@ use io_jail::{self, Minijail};
 use kvm::{Kvm, Vm, Vcpu, VcpuExit, IoeventAddress, NoDatamatch};
 use sys_util::{EventFd, MmapError, Killable, SignalFd, SignalFdError, Poller, Pollable,
                GuestMemory, Result as SysResult, Error as SysError,
-               register_signal_handler, SIGRTMIN,
+               register_signal_handler, block_signal, clear_signal, SIGRTMIN,
                geteuid, getegid};
 
 use Config;
@@ -307,10 +307,21 @@ pub fn run_vcpus(kvm: &Kvm,
             unsafe {
                 extern "C" fn handle_signal() {}
                 // Our signal handler does nothing and is trivially async signal safe.
+                // We need to install this signal handler even though we do block
+                // the signal below, to ensure that this signal will interrupt
+                // execution of KVM_RUN (this is implementation issue).
                 register_signal_handler(SIGRTMIN() + 0, handle_signal)
                     .expect("failed to register vcpu signal handler");
             }
 
+            // We do not really want the signal handler to run...
+            block_signal(SIGRTMIN() + 0)
+                .expect("failed to block signal");
+            // Tell KVM to not block anything when entering kvm run
+            // because we will be using first RT signal to kick the VCPU.
+            vcpu.set_signal_mask(&[])
+                .expect("failed to set up KVM VCPU signal mask");
+
             let res = vcpu_plugin.init(&vcpu);
             vcpu_thread_barrier.wait();
             if let Err(e) = res {
@@ -356,6 +367,11 @@ pub fn run_vcpus(kvm: &Kvm,
                         break;
                     }
 
+                    // Try to clear the signal that we use to kick VCPU if it is
+                    // pending before attempting to handle pause requests.
+                    clear_signal(SIGRTMIN() + 0)
+                        .expect("failed to clear pending signal");
+
                     if let Err(e) = vcpu_plugin.pre_run(&vcpu) {
                         error!("failed to process pause on vcpu {}: {:?}", cpu_id, e);
                         break;