summaryrefslogtreecommitdiffstats
path: root/debian/patches-rt/rtmutex-Make-lock_killable-work.patch
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches-rt/rtmutex-Make-lock_killable-work.patch')
-rw-r--r--debian/patches-rt/rtmutex-Make-lock_killable-work.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/debian/patches-rt/rtmutex-Make-lock_killable-work.patch b/debian/patches-rt/rtmutex-Make-lock_killable-work.patch
index a5cbaef9c..04c091d75 100644
--- a/debian/patches-rt/rtmutex-Make-lock_killable-work.patch
+++ b/debian/patches-rt/rtmutex-Make-lock_killable-work.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx@linutronix.de>
Date: Sat, 1 Apr 2017 12:50:59 +0200
Subject: [PATCH] rtmutex: Make lock_killable work
-Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.2/older/patches-5.2.17-rt9.tar.xz
+Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.4/older/patches-5.4.3-rt1.tar.xz
Locking an rt mutex killable does not work because signal handling is
restricted to TASK_INTERRUPTIBLE.
@@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
-@@ -1177,18 +1177,13 @@ static int __sched
+@@ -1200,18 +1200,13 @@ static int __sched
if (try_to_take_rt_mutex(lock, current, waiter))
break;