Suggestion needed to port the fix to JDK17 and JDK11S
Shruthi .
Shruthi.Shruthi1 at ibm.com
Wed Feb 26 10:58:17 UTC 2025
Hi Alan,
We checked with AIX team. And they are saying that It will be queued initially and in next few milli seconds it will be handled.
Thanks
Shruthi
________________________________
From: Alan Bateman <alan.bateman at oracle.com>
Sent: Tuesday, February 25, 2025 2:19 PM
To: Shruthi . <Shruthi.Shruthi1 at ibm.com>; net-dev at openjdk.org <net-dev at openjdk.org>
Cc: Syed Moinudeen <smoinud1 at in.ibm.com>
Subject: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and JDK11S
On 25/02/2025 08: 35, Shruthi . wrote: Hi Alan, Below is the response we got from the AIX team. ===>what happens if pthread_kill(thread, SGRTMAX-1) is called and the target thread is NOT in the read/write syscalls The expected behavior is
On 25/02/2025 08:35, Shruthi . wrote:
Hi Alan,
Below is the response we got from the AIX team.
===>what happens if pthread_kill(thread, SGRTMAX-1) is called and the target thread is NOT in the read/write syscalls
The expected behavior is thread will get interrupted and it will call the signal handler. in the case of this process it has a special signal handler for the signal 56. It will continue from the instruction it was in after returning back from the signal handler.
The question you need to answere is whether the signal is queued/pended when the target thread is not in a syscall. The behavior varies by OS, Linux and macOS are very different for example. None of the mails so far have been clear on what the behavior is on AIX so the proposed change may have the timing bug.
-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/net-dev/attachments/20250226/2c05ab64/attachment.htm>
More information about the net-dev
mailing list