I am less concerned about what else might be affected (if you are talking about applications) than about being in compliance with the specifications.If pthread_mutex_timedlock() would call pthread_mutex_take() with a intr value of false, instead of true as it is doing now, that would cause pthread_sem_take() to call nxsem_wait_uninterruptible(). But, I am *not* rushing to change this, because I don't know what else it might affect (and also I'm not 100% sure that my reading of the code is correct). In the meantime, I'll continue studying it.
- pthread_mutex_lock() and signals Nathan Hartman
- Re: pthread_mutex_lock() and signals Gregory Nutt
- Re: pthread_mutex_lock() and signals Gregory Nutt
- Re: pthread_mutex_lock() and signals Nathan Hartman
- Re: pthread_mutex_lock() and signals Gregory Nutt
- Re: pthread_mutex_lock() and signals Nathan Hartman
- Re: pthread_mutex_lock() and sign... Gregory Nutt
- Re: pthread_mutex_lock() and ... Nathan Hartman
- Re: pthread_mutex_lock() and ... Gregory Nutt
- Re: pthread_mutex_lock() and ... Nathan Hartman
- Re: pthread_mutex_lock() and ... Gregory Nutt
- Re: pthread_mutex_lock() and ... Nathan Hartman
- Re: pthread_mutex_lock() and ... Nathan Hartman