Re: mq_send()/mq_receive() may never return if used from threads

2025-01-28 Thread Corinna Vinschen via Cygwin
On Jan 28 09:00, Christian Franke via Cygwin wrote: > Corinna Vinschen via Cygwin wrote: > > On Jan 27 20:35, Corinna Vinschen via Cygwin wrote: > > > On Jan 27 19:59, Christian Franke via Cygwin wrote: > > > > Christian Franke wrote: > > > > > Found with 'stress-ng --workload ...': > > > > > > >

Re: mq_send()/mq_receive() may never return if used from threads

2025-01-28 Thread Christian Franke via Cygwin
Corinna Vinschen via Cygwin wrote: On Jan 27 20:35, Corinna Vinschen via Cygwin wrote: On Jan 27 19:59, Christian Franke via Cygwin wrote: Christian Franke wrote: Found with 'stress-ng --workload ...': If mq_receive is called on an empty queue and mq_send is called later from a different thre

Re: mq_send()/mq_receive() may never return if used from threads

2025-01-27 Thread Corinna Vinschen via Cygwin
On Jan 27 20:35, Corinna Vinschen via Cygwin wrote: > On Jan 27 19:59, Christian Franke via Cygwin wrote: > > Christian Franke wrote: > > > Found with 'stress-ng --workload ...': > > > > > > If mq_receive is called on an empty queue and mq_send is called later > > > from a different thread, both f

Re: mq_send()/mq_receive() may never return if used from threads

2025-01-27 Thread Corinna Vinschen via Cygwin
On Jan 27 19:59, Christian Franke via Cygwin wrote: > Christian Franke wrote: > > Found with 'stress-ng --workload ...': > > > > If mq_receive is called on an empty queue and mq_send is called later > > from a different thread, both functions never return and signals > > (including SIGKILL) are no

Re: mq_send()/mq_receive() may never return if used from threads

2025-01-27 Thread Christian Franke via Cygwin
Christian Franke wrote: Found with 'stress-ng --workload ...': If mq_receive is called on an empty queue and mq_send is called later from a different thread, both functions never return and signals (including SIGKILL) are no longer processed. Testcase (attached): $ uname -r 3.5.5-1.x86_64

mq_send()/mq_receive() may never return if used from threads

2025-01-17 Thread Christian Franke via Cygwin
Found with 'stress-ng --workload ...': If mq_receive is called on an empty queue and mq_send is called later from a different thread, both functions never return and signals (including SIGKILL) are no longer processed. Testcase (attached): $ uname -r 3.5.5-1.x86_64 $ gcc -o mqhang mqhang.c