On 7/22/24 22:30, Dev Jain wrote:
On 7/22/24 20:28, Shuah Khan wrote:
On 7/15/24 05:49, Dev Jain wrote:
On 6/30/24 20:48, Oleg Nesterov wrote:
I see nothing wrong, but perhaps this test can be simplified?
Feel free to ignore.
Say,
On 06/27, Dev Jain wrote:
+void handler_usr(int signo, sig
On 7/22/24 20:28, Shuah Khan wrote:
On 7/15/24 05:49, Dev Jain wrote:
On 6/30/24 20:48, Oleg Nesterov wrote:
I see nothing wrong, but perhaps this test can be simplified?
Feel free to ignore.
Say,
On 06/27, Dev Jain wrote:
+void handler_usr(int signo, siginfo_t *info, void *uc)
+{
+ in
On 7/15/24 05:49, Dev Jain wrote:
On 6/30/24 20:48, Oleg Nesterov wrote:
I see nothing wrong, but perhaps this test can be simplified?
Feel free to ignore.
Say,
On 06/27, Dev Jain wrote:
+void handler_usr(int signo, siginfo_t *info, void *uc)
+{
+ int ret;
+
+ /*
+ * Break out of i
On 6/30/24 20:48, Oleg Nesterov wrote:
I see nothing wrong, but perhaps this test can be simplified?
Feel free to ignore.
Say,
On 06/27, Dev Jain wrote:
+void handler_usr(int signo, siginfo_t *info, void *uc)
+{
+ int ret;
+
+ /*
+* Break out of infinite recursion caused
I see nothing wrong, but perhaps this test can be simplified?
Feel free to ignore.
Say,
On 06/27, Dev Jain wrote:
>
> +void handler_usr(int signo, siginfo_t *info, void *uc)
> +{
> + int ret;
> +
> + /*
> + * Break out of infinite recursion caused by raise(SIGUSR1) invoked
> + *
On Thu, Jun 27, 2024 at 09:22:15AM +0530, Dev Jain wrote:
> This test asserts the relation between blocked signal, delivered signal,
> and ucontext. The ucontext is mangled with, by adding a signal mask to
> it; on return from the handler, the thread must block the corresponding
> signal.
Reviewed
This test asserts the relation between blocked signal, delivered signal,
and ucontext. The ucontext is mangled with, by adding a signal mask to
it; on return from the handler, the thread must block the corresponding
signal.
In the test description, I have also described signal delivery and blockag
