According the ww-mutex-design.txt documentation, the
ww_mutex_lock_interruptible and ww_mutex_lock functions should return -EDEADLK
when faced with a deadlock. To do so, the flag detect_deadlock in the
rt_mutex_slowlock calls should be enabled. This patch corrects potential
deadlocks when
PREEMPT_RT with nouveau driver.
PS: Sorry to post again, CC'ing -rt maintainers now.
Signed-off-by: Gustavo Bittencourt gbit...@gmail.com
---
kernel/locking/rtmutex.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index
On Sat, Mar 7, 2015 at 11:15 AM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
I'm pleased to announce the v3.18.9-rt4 patch set.
Changes since v3.18.9-rt3
Has v3.18.9-rt3 been released? If so, I missed the announcement.
--
To unsubscribe from this list: send the line unsubscribe
On Tue, Feb 24, 2015 at 2:50 PM, Mike Galbraith
umgwanakikb...@gmail.com wrote:
On Tue, 2015-02-24 at 13:19 -0300, Gustavo Bittencourt wrote:
The deadlock returned after I applied this patch in v3.18.7-rt2. Here is my
log:
Hrmph. I definitely want your patch to die ;-) It adds a whole
On Tue, Feb 24, 2015 at 10:41 AM, Mike Galbraith
umgwanakikb...@gmail.com wrote:
locking, ww_mutex: fix ww_mutex vs self-deadlock
If the caller already holds the mutex, task_blocks_on_rt_mutex()
returns -EDEADLK, we proceed directly to rt_mutex_handle_deadlock()
where it's instant game over.
On Thu, Feb 26, 2015 at 5:02 AM, Mike Galbraith
umgwanakikb...@gmail.com wrote:
On Tue, 2015-02-24 at 13:19 -0300, Gustavo Bittencourt wrote:
The deadlock returned after I applied this patch in v3.18.7-rt2.
Grr, because dummy here munged a reject when he backported to 3.18-rt.
Please try
running PREEMPT_RT with nouveau driver.
Kernel v3.14-rt
Signed-off-by: Gustavo Bittencourt
---
kernel/locking/rtmutex.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index 6c40660..3f6ef91 100644
--- a/kernel/locking
PREEMPT_RT with nouveau driver.
PS: Sorry to post again, CC'ing -rt maintainers now.
Signed-off-by: Gustavo Bittencourt
---
kernel/locking/rtmutex.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index 6c40660..3f6ef91
On Tue, Feb 24, 2015 at 10:41 AM, Mike Galbraith
wrote:
> locking, ww_mutex: fix ww_mutex vs self-deadlock
>
> If the caller already holds the mutex, task_blocks_on_rt_mutex()
> returns -EDEADLK, we proceed directly to rt_mutex_handle_deadlock()
> where it's instant game over.
>
> Let ww_mutexes
On Tue, Feb 24, 2015 at 2:50 PM, Mike Galbraith
wrote:
> On Tue, 2015-02-24 at 13:19 -0300, Gustavo Bittencourt wrote:
>>
>> The deadlock returned after I applied this patch in v3.18.7-rt2. Here is my
>> log:
>
>
> Hrmph. I definitely want your patch to die ;-) I
On Thu, Feb 26, 2015 at 5:02 AM, Mike Galbraith
wrote:
> On Tue, 2015-02-24 at 13:19 -0300, Gustavo Bittencourt wrote:
>
>> The deadlock returned after I applied this patch in v3.18.7-rt2.
>
> Grr, because dummy here munged a reject when he backported to 3.18-rt.
> Please try
On Sat, Mar 7, 2015 at 11:15 AM, Sebastian Andrzej Siewior
wrote:
>
> I'm pleased to announce the v3.18.9-rt4 patch set.
>
> Changes since v3.18.9-rt3
>
Has v3.18.9-rt3 been released? If so, I missed the announcement.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
12 matches
Mail list logo
