This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/22396] x86-64: siglongjmp does not restore PKRU register


https://sourceware.org/bugzilla/show_bug.cgi?id=22396

--- Comment #8 from Andreas Schwab <schwab@linux-m68k.org> ---
It's not a matter of async vs sync signals, only the property of the
interrupted function matters:

"Although longjmp() is an async-signal-safe function, if it is invoked from a
signal handler which interrupted a non-async-signal-safe function or equivalent
(such as the processing equivalent to exit() performed after a return from the
initial call to main()), the behavior of any subsequent call to a
non-async-signal-safe function or equivalent is undefined."

Thus a handler for a synchronously-generated signal that interrupted a
non-async-signal-safe function has the same restrictions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]