2020-09-04 20:10:21 +00:00
|
|
|
From d90aaa0388b133d510b0f4c2a2cbc62a2201cdb0 Mon Sep 17 00:00:00 2001
|
|
|
|
Message-Id: <d90aaa0388b133d510b0f4c2a2cbc62a2201cdb0.1599166691.git.zanussi@kernel.org>
|
|
|
|
In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org>
|
|
|
|
References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org>
|
2019-08-18 21:33:52 +00:00
|
|
|
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
|
|
|
|
Date: Wed, 26 Jun 2019 17:44:27 +0200
|
2020-09-04 20:10:21 +00:00
|
|
|
Subject: [PATCH 275/333] Revert "futex: workaround migrate_disable/enable in
|
2019-08-18 21:33:52 +00:00
|
|
|
different context"
|
2020-09-04 20:10:21 +00:00
|
|
|
Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz
|
2019-08-18 21:33:52 +00:00
|
|
|
|
|
|
|
[ Upstream commit a71221d81cc4873891ae44f3aa02df596079b786 ]
|
|
|
|
|
|
|
|
Drop the RT fixup, the futex code will be changed to avoid the need for
|
|
|
|
the workaround.
|
|
|
|
|
|
|
|
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
|
|
|
|
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
|
|
|
|
---
|
|
|
|
kernel/futex.c | 19 -------------------
|
|
|
|
1 file changed, 19 deletions(-)
|
|
|
|
|
|
|
|
diff --git a/kernel/futex.c b/kernel/futex.c
|
2020-04-21 20:13:52 +00:00
|
|
|
index 1f9dd186b00c..9900c3f30124 100644
|
2019-08-18 21:33:52 +00:00
|
|
|
--- a/kernel/futex.c
|
|
|
|
+++ b/kernel/futex.c
|
2020-04-21 20:13:52 +00:00
|
|
|
@@ -2895,14 +2895,6 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
|
2019-08-18 21:33:52 +00:00
|
|
|
* before __rt_mutex_start_proxy_lock() is done.
|
|
|
|
*/
|
|
|
|
raw_spin_lock_irq(&q.pi_state->pi_mutex.wait_lock);
|
|
|
|
- /*
|
|
|
|
- * the migrate_disable() here disables migration in the in_atomic() fast
|
|
|
|
- * path which is enabled again in the following spin_unlock(). We have
|
|
|
|
- * one migrate_disable() pending in the slow-path which is reversed
|
|
|
|
- * after the raw_spin_unlock_irq() where we leave the atomic context.
|
|
|
|
- */
|
|
|
|
- migrate_disable();
|
|
|
|
-
|
|
|
|
spin_unlock(q.lock_ptr);
|
|
|
|
/*
|
|
|
|
* __rt_mutex_start_proxy_lock() unconditionally enqueues the @rt_waiter
|
2020-04-21 20:13:52 +00:00
|
|
|
@@ -2911,7 +2903,6 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
|
2019-08-18 21:33:52 +00:00
|
|
|
*/
|
|
|
|
ret = __rt_mutex_start_proxy_lock(&q.pi_state->pi_mutex, &rt_waiter, current);
|
|
|
|
raw_spin_unlock_irq(&q.pi_state->pi_mutex.wait_lock);
|
|
|
|
- migrate_enable();
|
|
|
|
|
|
|
|
if (ret) {
|
|
|
|
if (ret == 1)
|
2020-04-21 20:13:52 +00:00
|
|
|
@@ -3060,21 +3051,11 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
|
2019-08-18 21:33:52 +00:00
|
|
|
* rt_waiter. Also see the WARN in wake_futex_pi().
|
|
|
|
*/
|
|
|
|
raw_spin_lock_irq(&pi_state->pi_mutex.wait_lock);
|
|
|
|
- /*
|
|
|
|
- * Magic trickery for now to make the RT migrate disable
|
|
|
|
- * logic happy. The following spin_unlock() happens with
|
|
|
|
- * interrupts disabled so the internal migrate_enable()
|
|
|
|
- * won't undo the migrate_disable() which was issued when
|
|
|
|
- * locking hb->lock.
|
|
|
|
- */
|
|
|
|
- migrate_disable();
|
|
|
|
spin_unlock(&hb->lock);
|
|
|
|
|
|
|
|
/* drops pi_state->pi_mutex.wait_lock */
|
|
|
|
ret = wake_futex_pi(uaddr, uval, pi_state);
|
|
|
|
|
|
|
|
- migrate_enable();
|
|
|
|
-
|
|
|
|
put_pi_state(pi_state);
|
|
|
|
|
|
|
|
/*
|
2020-01-03 23:36:11 +00:00
|
|
|
--
|
2020-06-22 13:14:16 +00:00
|
|
|
2.17.1
|
2020-01-03 23:36:11 +00:00
|
|
|
|