summaryrefslogtreecommitdiffstats
path: root/kernel/crash_dump.c
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2021-09-01 22:30:27 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2021-09-22 16:24:01 +0200
commita68de80f61f6af397bc06fb391ff2e571c9c4d80 (patch)
tree6ff39a232fc62d4eba20aedea314073723bc9fce /kernel/crash_dump.c
parentKVM: rseq: Update rseq when processing NOTIFY_RESUME on xfer to KVM guest (diff)
downloadlinux-a68de80f61f6af397bc06fb391ff2e571c9c4d80.tar.xz
linux-a68de80f61f6af397bc06fb391ff2e571c9c4d80.zip
entry: rseq: Call rseq_handle_notify_resume() in tracehook_notify_resume()
Invoke rseq_handle_notify_resume() from tracehook_notify_resume() now that the two function are always called back-to-back by architectures that have rseq. The rseq helper is stubbed out for architectures that don't support rseq, i.e. this is a nop across the board. Note, tracehook_notify_resume() is horribly named and arguably does not belong in tracehook.h as literally every line of code in it has nothing to do with tracing. But, that's been true since commit a42c6ded827d ("move key_repace_session_keyring() into tracehook_notify_resume()") first usurped tracehook_notify_resume() back in 2012. Punt cleaning that mess up to future patches. No functional change intended. Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Signed-off-by: Sean Christopherson <seanjc@google.com> Message-Id: <20210901203030.1292304-3-seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'kernel/crash_dump.c')
0 files changed, 0 insertions, 0 deletions