Messages in this thread | | | Date | Wed, 31 Mar 2004 09:38:33 -0800 | From | Dirk Morris <> | Subject | Re: [2.6.2] Badness in futex_wait revisited |
| |
No, I still get them in 2.6.4
To my knowledge, they only happen when one thread is blocked in a system call and another thread makes a system("foo bar") call. The blocked thread will return with EINTR. I see this usually in sem_wait, but also in epoll_wait sometimes.
Is it possible system() is causing the wrong process to get woken up?
Let me know if you need any further information, I can reproduce it consistently.
Jamie Lokier wrote:
>Was the badness in futex_wait problem ever resolved? > >-- Jamie > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |