summaryrefslogtreecommitdiffstats
path: root/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch')
-rw-r--r--debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch b/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch
index 394058af8..865eee08c 100644
--- a/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch
+++ b/debian/patches-rt/0136-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 136/342] rtmutex: Make lock_killable work
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=61fa01d84f2b1b35d66b69c4b7fda86f45ad7d50
+Subject: [PATCH 136/351] rtmutex: Make lock_killable work
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fbf7123998ba54e81012475000c6708088804590
Locking an rt mutex killable does not work because signal handling is
restricted to TASK_INTERRUPTIBLE.