RFR: 8282475: SafeFetch should not rely on existence of Thread::current [v6]

[David Holmes]

On Thu, 10 Mar 2022 12:31:06 GMT, Anton Kozlov <akozlov at openjdk.org> wrote:

> The signal mask is per-thread, and a native thread may block the JVM signal.

@AntonKozlov the signal from safefetch (if it is not safe) is a SIGSEGV or SIGBUS. If these signals happen to be blocked and we raise the signal synchronously then we are in undefined behaviour territory. So I guess in that sense yes safefetch is not guaranteed to be safe.

-------------

PR: https://git.openjdk.java.net/jdk/pull/7727