Re: [PATCH net-next v2 3/3] connector/cn_proc: Selftest for threads

2024-10-16 Thread Anjali Kulkarni
> On Oct 15, 2024, at 5:32 PM, Liam Howlett wrote: > > * Anjali Kulkarni [241015 17:28]: >> >> >>> On Oct 15, 2024, at 12:27 PM, Liam Howlett wrote: >>> >>> * Anjali Kulkarni [241015 13:30]: Test to check if setting PROC_CN_MCAST_NOTIFY in proc connector API, allows a thread's n

Re: [PATCH net-next v2 3/3] connector/cn_proc: Selftest for threads

2024-10-15 Thread Liam R. Howlett
* Anjali Kulkarni [241015 17:28]: > > > > On Oct 15, 2024, at 12:27 PM, Liam Howlett wrote: > > > > * Anjali Kulkarni [241015 13:30]: > >> Test to check if setting PROC_CN_MCAST_NOTIFY in proc connector API, allows > >> a thread's non-zero exit status to be returned to proc_filter. > >> > >>

Re: [PATCH net-next v2 3/3] connector/cn_proc: Selftest for threads

2024-10-15 Thread Anjali Kulkarni
> On Oct 15, 2024, at 12:27 PM, Liam Howlett wrote: > > * Anjali Kulkarni [241015 13:30]: >> Test to check if setting PROC_CN_MCAST_NOTIFY in proc connector API, allows >> a thread's non-zero exit status to be returned to proc_filter. >> >> The threads.c program creates 2 child threads. 1st t

Re: [PATCH net-next v2 3/3] connector/cn_proc: Selftest for threads

2024-10-15 Thread Liam R. Howlett
* Anjali Kulkarni [241015 13:30]: > Test to check if setting PROC_CN_MCAST_NOTIFY in proc connector API, allows > a thread's non-zero exit status to be returned to proc_filter. > > The threads.c program creates 2 child threads. 1st thread handles signal > SIGSEGV, and 2nd thread needs to indicate

[PATCH net-next v2 3/3] connector/cn_proc: Selftest for threads

2024-10-15 Thread Anjali Kulkarni
Test to check if setting PROC_CN_MCAST_NOTIFY in proc connector API, allows a thread's non-zero exit status to be returned to proc_filter. The threads.c program creates 2 child threads. 1st thread handles signal SIGSEGV, and 2nd thread needs to indicate some error condition (value 1) to the kernel