Andrei Vagin 8890371e35 platform/kvm: use per-thread signal stack to run bluepill handler ...

The user-space bluepill introduced the issue. With that change, we use a
per-vcpu stack to run bluepillHandler. BluepillHanlder releases a vcpu before
calling sigreturn, so it is still running on the vcpu stack. The race looks
like this: one thread releases a vcpu, another thread takes it and  starts
using its stack, the first thread calls sigreturn with a corrupted signal
frame.



PiperOrigin-RevId: 684992950

2024-10-11 16:40:39 -07:00

..

BUILD

platform/kvm: use per-thread signal stack to run bluepill handler

2024-10-11 16:40:39 -07:00

sigframe_amd64_test.go

platform/kvm: use per-thread signal stack to run bluepill handler

2024-10-11 16:40:39 -07:00

sigframe_amd64_test.s

platform/kvm: rewriting bluepill() without signal handler trampolining

2024-08-19 14:50:36 -07:00

sigframe_amd64_unsafe.go

platform/kvm: use per-thread signal stack to run bluepill handler

2024-10-11 16:40:39 -07:00

sigframe_amd64.s

platform/kvm: use per-thread signal stack to run bluepill handler

2024-10-11 16:40:39 -07:00

sigframe_test.go

platform/kvm: rewriting bluepill() without signal handler trampolining

2024-08-19 14:50:36 -07:00

sigframe.go

platform/kvm: rewriting bluepill() without signal handler trampolining

2024-08-19 14:50:36 -07:00