Re: [PATCH 3/3] locking: rtmutex: set state back to running on error

2015-02-28 Thread Mike Galbraith
On Fri, 2015-02-27 at 17:57 +0100, Sebastian Andrzej Siewior wrote: > The "usual" path is: > - rt_mutex_slowlock() > - set_current_state() > - task_blocks_on_rt_mutex() (ret 0) > - __rt_mutex_slowlock() >- sleep or not but do return with __set_current_state(TASK_RUNNING) > - back to

Re: [PATCH 3/3] locking: rtmutex: set state back to running on error

2015-02-28 Thread Mike Galbraith
On Fri, 2015-02-27 at 17:57 +0100, Sebastian Andrzej Siewior wrote: The usual path is: - rt_mutex_slowlock() - set_current_state() - task_blocks_on_rt_mutex() (ret 0) - __rt_mutex_slowlock() - sleep or not but do return with __set_current_state(TASK_RUNNING) - back to caller. In

[PATCH 3/3] locking: rtmutex: set state back to running on error

2015-02-27 Thread Sebastian Andrzej Siewior
The "usual" path is: - rt_mutex_slowlock() - set_current_state() - task_blocks_on_rt_mutex() (ret 0) - __rt_mutex_slowlock() - sleep or not but do return with __set_current_state(TASK_RUNNING) - back to caller. In the early error case where task_blocks_on_rt_mutex() return -EDEADLK we

[PATCH 3/3] locking: rtmutex: set state back to running on error

2015-02-27 Thread Sebastian Andrzej Siewior
The usual path is: - rt_mutex_slowlock() - set_current_state() - task_blocks_on_rt_mutex() (ret 0) - __rt_mutex_slowlock() - sleep or not but do return with __set_current_state(TASK_RUNNING) - back to caller. In the early error case where task_blocks_on_rt_mutex() return -EDEADLK we never