diff options
Diffstat (limited to 'debian/patches-rt/0015-sched-lockdep-Annotate-pi_lock-recursion.patch')
| -rw-r--r-- | debian/patches-rt/0015-sched-lockdep-Annotate-pi_lock-recursion.patch | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/debian/patches-rt/0015-sched-lockdep-Annotate-pi_lock-recursion.patch b/debian/patches-rt/0015-sched-lockdep-Annotate-pi_lock-recursion.patch index 05030516b..db126bb82 100644 --- a/debian/patches-rt/0015-sched-lockdep-Annotate-pi_lock-recursion.patch +++ b/debian/patches-rt/0015-sched-lockdep-Annotate-pi_lock-recursion.patch @@ -1,8 +1,8 @@ -From c0e34a5ef4e854220a216e934ab90f04d4432bdd Mon Sep 17 00:00:00 2001 +From 08be58930a1822de1d0df49597950a0a0f43d407 Mon Sep 17 00:00:00 2001 From: Peter Zijlstra <peterz@infradead.org> Date: Fri, 23 Oct 2020 12:12:12 +0200 Subject: [PATCH 015/323] sched, lockdep: Annotate ->pi_lock recursion -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.10/older/patches-5.10.204-rt100.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.10/older/patches-5.10.215-rt107.tar.xz There's a valid ->pi_lock recursion issue where the actual PI code tries to wake up the stop task. Make lockdep aware so it doesn't @@ -15,7 +15,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> 1 file changed, 15 insertions(+) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 2517a003295b..abbf01f77a76 100644 +index 2517a003295b9..abbf01f77a76f 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -2670,6 +2670,7 @@ int select_task_rq(struct task_struct *p, int cpu, int sd_flags, int wake_flags) @@ -48,5 +48,5 @@ index 2517a003295b..abbf01f77a76 100644 cpu_rq(cpu)->stop = stop; -- -2.43.0 +2.44.0 |