Disconnect call-chain between sighandler() and bluepill().

When sentry is running in guest ring0, the goroutine stack is changing
and it will not be the stack when bluepill() is called.

If PMU interrupt hits when the CPU is in host ring 0, the perf handler
will try to get the stack of the kernel and the userspace(sentry).  It
can travel back to sighandler() and try to continue to the stack of
the goroutine with the outdated frame pointer if sentry has been running
in the guest.  The perf handler can't record correct addresses
from the outdated and wrong frames.  Those addresses are often
irresolvable, and even if it is resolvable accidentally, it would
be misleading names.

To fix the problem, we just set the frame pointer(%RBP) to zero and
disconnect the link when the zeroed frame pointer is saved in the
frame in bluepillHandler().

Signed-off-by: Lai Jiangshan <jiangshan.ljs@antfin.com>

0 files changed, 0 insertions, 0 deletions