Google Git
Sign in
android / platform / external / crosvm / 55a68e9209f20bd33a4a037df63681843afb4f4d
commit55a68e9209f20bd33a4a037df63681843afb4f4d[log] [tgz]
authorSebastian Ene <sebastianene@google.com>Mon Oct 16 10:29:42 2023 +0000
committercrosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Oct 17 17:11:19 2023 +0000
tree48d93c5ad8610e895932c32529294d71e18c0ed8
parentafe326684895592db15d582968a2ffe9461f680e [diff]
devices: vmwdt: Fix race condition on VM reset

When the vCPU threads are shutting down, a message is sent to the vmwdt worker
thread to stop polling for timer expiration events. If there are pending
timer expiration events, they are processed while the VCPU thread is
dead. This triggers a panic message because the stat file for the
corresponding VCPU thread is not found.
Verify if there are pending shutdown events before dealing with the
timer events. Allow get_guest_time_ms() to fail without panic if there
is no stat entry found for the current vcpu.

BUG=b:305630196
TEST=manual testing build and Virtualization apk on a Husky device

Change-Id: I546c230a15341eda647800634421ae3289ca5049
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4943010
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Sebastian Ene <sebastianene@google.com>
1 file changed
tree: 48d93c5ad8610e895932c32529294d71e18c0ed8
  1. .cargo/
  2. .config/
  3. .devcontainer/
  4. .github/
  5. .vscode/
  6. aarch64/
  7. acpi_tables/
  8. arch/
  9. argh_helpers/
  10. audio_streams_conformance_test/
  11. audio_util/
  12. base/
  13. bit_field/
  14. broker_ipc/
  15. common/
  16. cros_async/
  17. cros_fdt/
  18. cros_tracing/
  19. cros_tracing_types/
  20. crosvm_cli/
  21. crosvm_control/
  22. crosvm_plugin/
  23. devices/
  24. disk/
  25. docs/
  26. e2e_tests/
  27. fuse/
  28. fuzz/
  29. gpu_display/
  30. hypervisor/
  31. infra/
  32. io_uring/
  33. jail/
  34. kernel_cmdline/
  35. kernel_loader/
  36. kvm/
  37. kvm_sys/
  38. libcras_stub/
  39. linux_input_sys/
  40. logo/
  41. media/
  42. metrics/
  43. net_sys/
  44. net_util/
  45. perfetto/
  46. power_monitor/
  47. prebuilts/
  48. proto_build_tools/
  49. protos/
  50. resources/
  51. riscv64/
  52. rutabaga_gfx/
  53. sandbox/
  54. serde_keyvalue/
  55. src/
  56. swap/
  57. system_api/
  58. tests/
  59. third_party/
  60. tools/
  61. tube_transporter/
  62. usb_sys/
  63. usb_util/
  64. vendor/
  65. vfio_sys/
  66. vhost/
  67. virtio_sys/
  68. vm_control/
  69. vm_memory/
  70. win_audio/
  71. win_util/
  72. x86_64/
  73. .dockerignore
  74. .envrc
  75. .gitignore
  76. .gitmodules
  77. .rustfmt.toml
  78. ARCHITECTURE.md
  79. Cargo.lock
  80. Cargo.toml
  81. CONTRIBUTING.md
  82. DIR_METADATA
  83. LICENSE
  84. mypy.ini
  85. OWNERS
  86. OWNERS_COUNCIL
  87. PRESUBMIT.cfg
  88. pyproject.toml
  89. README.chromeos.md
  90. README.md
  91. rust-toolchain
README.md

crosvm - The ChromeOS Virtual Machine Monitor

crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the ChromeOS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.

crosvm is currently used to run Linux/Android guests on ChromeOS devices.

Logo