rt-kernel: upgrade to 4.9.333-rt197

RT-Kernel upgrade from 4.9.299-rt191 to 4.9.333-rt197
Patches starting with 1000- are NV specific patches.

1007-WIP-miscellaneous-issues-with-4.9.333.patch was added
for this realease.

Bug 3823963
Bug 2969628
Bug 3819327

Change-Id: I246143d64c7fc88565c9dd9e7357364c46c87334
Signed-off-by: Chaitanya Namuduri <[email protected]>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-4.9/+/2816732
Tested-by: Dmitry Pervushin <[email protected]>
Reviewed-by: Dmitry Pervushin <[email protected]>

rt-patches/0001-timer-make-the-base-lock-raw.patch

@@ -1,7 +1,7 @@
-From a1d5c2a9985d7682b16a52bb4d0fca4c9caeada3 Mon Sep 17 00:00:00 2001
+From 17333cab43d63daef60e8afc1cc460fb6a08c112 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <[email protected]>
 Date: Wed, 13 Jul 2016 18:22:23 +0200
-Subject: [PATCH 001/352] timer: make the base lock raw
+Subject: [PATCH 001/364] timer: make the base lock raw
 
 The part where the base lock is held got more predictable / shorter after the
 timer rework. One reason is the lack of re-cascading.

rt-patches/0002-lockdep-Handle-statically-initialized-PER_CPU-locks-.patch

@@ -1,7 +1,7 @@
-From b0c7d6edbd18d4786f2d9091fcf97aef5b012ed2 Mon Sep 17 00:00:00 2001
+From 6ade91ac7b9fd694be03fe88f1c3a03d5dc7902d Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <[email protected]>
 Date: Fri, 17 Feb 2017 19:44:39 +0100
-Subject: [PATCH 002/352] lockdep: Handle statically initialized PER_CPU locks
+Subject: [PATCH 002/364] lockdep: Handle statically initialized PER_CPU locks
  proper
 
 If a PER_CPU struct which contains a spin_lock is statically initialized
@@ -45,7 +45,7 @@ Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
  5 files changed, 67 insertions(+), 36 deletions(-)
 
 diff --git a/include/linux/module.h b/include/linux/module.h
-index 49f0aae..ee6f07f 100644
+index 70e49db..858088e 100644
 --- a/include/linux/module.h
 +++ b/include/linux/module.h
 @@ -501,6 +501,7 @@ static inline int module_is_live(struct module *mod)

rt-patches/0003-lockdep-Fix-compilation-error-for-CONFIG_MODULES-and.patch

@@ -1,7 +1,7 @@
-From 84937749f5b432e9a5e8843d14a710a002ad069c Mon Sep 17 00:00:00 2001
+From bbb7a46d3f93278a0cfaa9ae88a3980500a9c82d Mon Sep 17 00:00:00 2001
 From: Dan Murphy <[email protected]>
 Date: Fri, 24 Feb 2017 08:41:49 -0600
-Subject: [PATCH 003/352] lockdep: Fix compilation error for !CONFIG_MODULES
+Subject: [PATCH 003/364] lockdep: Fix compilation error for !CONFIG_MODULES
  and !CONFIG_SMP
 
 When CONFIG_MODULES is not set then it fails to compile in lockdep:
@@ -27,7 +27,7 @@ Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
  2 files changed, 10 insertions(+)
 
 diff --git a/include/linux/module.h b/include/linux/module.h
-index ee6f07f..fb10e0a 100644
+index 858088e..7a5a15b 100644
 --- a/include/linux/module.h
 +++ b/include/linux/module.h
 @@ -669,6 +669,11 @@ static inline bool is_module_percpu_address(unsigned long addr)

rt-patches/0004-lockdep-Fix-per-cpu-static-objects.patch

@@ -1,7 +1,7 @@
-From 9f34a2bda4b9432d7fb07f692ffe2d51ae48d5a8 Mon Sep 17 00:00:00 2001
+From 595fbde634fc7c6e39cfe5e43a644692c0726a1f Mon Sep 17 00:00:00 2001
 From: Peter Zijlstra <[email protected]>
 Date: Mon, 20 Mar 2017 12:26:55 +0100
-Subject: [PATCH 004/352] lockdep: Fix per-cpu static objects
+Subject: [PATCH 004/364] lockdep: Fix per-cpu static objects
 
 Since commit 383776fa7527 ("locking/lockdep: Handle statically initialized
 PER_CPU locks properly") we try to collapse per-cpu locks into a single
@@ -72,10 +72,10 @@ index 8e0cb7a..68123c1 100644
 
  /*
 diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 41dd49a..c135d54 100644
+index 9c62fa5..f7dc3ea 100644
 --- a/kernel/cpu.c
 +++ b/kernel/cpu.c
-@@ -1396,6 +1396,8 @@ core_initcall(cpu_hotplug_pm_sync_init);
+@@ -1397,6 +1397,8 @@ core_initcall(cpu_hotplug_pm_sync_init);
 
  #endif /* CONFIG_PM_SLEEP_SMP */
 
@@ -84,7 +84,7 @@ index 41dd49a..c135d54 100644
  #endif /* CONFIG_SMP */
 
  /* Boot processor state steps */
-@@ -2245,6 +2247,10 @@ void __init boot_cpu_init(void)
+@@ -2256,6 +2258,10 @@ void __init boot_cpu_init(void)
  	set_cpu_active(cpu, true);
  	set_cpu_present(cpu, true);
  	set_cpu_possible(cpu, true);

rt-patches/0005-rtmutex-Deboost-before-waking-up-the-top-waiter.patch

@@ -1,7 +1,7 @@
-From b89905f08a808b54c4b04f3f1cc75dcd88b8425e Mon Sep 17 00:00:00 2001
+From f020c6700a51bd70eb56c0100d2cd39cb0a3da26 Mon Sep 17 00:00:00 2001
 From: Xunlei Pang <[email protected]>
 Date: Thu, 23 Mar 2017 15:56:07 +0100
-Subject: [PATCH 005/352] rtmutex: Deboost before waking up the top waiter
+Subject: [PATCH 005/364] rtmutex: Deboost before waking up the top waiter
 
 Upstream commit 2a1c6029940675abb2217b590512dbf691867ec4
 

rt-patches/0006-sched-rtmutex-deadline-Fix-a-PI-crash-for-deadline-t.patch

@@ -1,7 +1,7 @@
-From b94c2e8cc1c3d8e37c7f091d62e72460c05ccd75 Mon Sep 17 00:00:00 2001
+From 05b8f87937cbd24dff467e2f4fde08367ec17476 Mon Sep 17 00:00:00 2001
 From: Xunlei Pang <[email protected]>
 Date: Thu, 23 Mar 2017 15:56:08 +0100
-Subject: [PATCH 006/352] sched/rtmutex/deadline: Fix a PI crash for deadline
+Subject: [PATCH 006/364] sched/rtmutex/deadline: Fix a PI crash for deadline
  tasks
 
 Upstream commit e96a7705e7d3fef96aec9b590c63b2f6f7d2ba22
@@ -73,10 +73,10 @@ index 325f649..d359b1a 100644
  #else
  # define INIT_RT_MUTEXES(tsk)
 diff --git a/include/linux/sched.h b/include/linux/sched.h
-index cc34dc3..4ca49eb 100644
+index 00fedaa..82c695f 100644
 --- a/include/linux/sched.h
 +++ b/include/linux/sched.h
-@@ -1898,6 +1898,8 @@ struct task_struct {
+@@ -1842,6 +1842,8 @@ struct task_struct {
  	/* PI waiters blocked on a rt_mutex held by this task */
  	struct rb_root pi_waiters;
  	struct rb_node *pi_waiters_leftmost;
@@ -98,10 +98,10 @@ index a30b172..60d0c47 100644
  extern void rt_mutex_adjust_pi(struct task_struct *p);
  static inline bool tsk_is_pi_blocked(struct task_struct *tsk)
 diff --git a/kernel/fork.c b/kernel/fork.c
-index 33548a6..c61b822 100644
+index 3b0f82a..8a1c784 100644
 --- a/kernel/fork.c
 +++ b/kernel/fork.c
-@@ -1441,6 +1441,7 @@ static void rt_mutex_init_task(struct task_struct *p)
+@@ -1443,6 +1443,7 @@ static void rt_mutex_init_task(struct task_struct *p)
  #ifdef CONFIG_RT_MUTEXES
  	p->pi_waiters = RB_ROOT;
  	p->pi_waiters_leftmost = NULL;
@@ -168,10 +168,10 @@ index ceaf15b..783cad5 100644
 
  /*
 diff --git a/kernel/sched/core.c b/kernel/sched/core.c
-index d5ab608..0545760 100644
+index 7085aaa..b057aba 100644
 --- a/kernel/sched/core.c
 +++ b/kernel/sched/core.c
-@@ -3795,6 +3795,8 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
+@@ -3788,6 +3788,8 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
  		goto out_unlock;
  	}
 

rt-patches/0007-sched-deadline-rtmutex-Dont-miss-the-dl_runtime-dl_p.patch

@@ -1,7 +1,7 @@
-From 329a3f1542a25d19499c4186b38051052a9dc5bb Mon Sep 17 00:00:00 2001
+From f55fba2f566809ca54e20575cbf78c05f029898e Mon Sep 17 00:00:00 2001
 From: Xunlei Pang <[email protected]>
 Date: Thu, 23 Mar 2017 15:56:09 +0100
-Subject: [PATCH 007/352] sched/deadline/rtmutex: Dont miss the
+Subject: [PATCH 007/364] sched/deadline/rtmutex: Dont miss the
  dl_runtime/dl_period update
 
 Upstream commit 85e2d4f992868ad78dc8bb2c077b652fcfb3661a

rt-patches/0008-rtmutex-Clean-up.patch

@@ -1,7 +1,7 @@
-From 114ac9e1f932162a82b9b2d77e8ca97cf184b28d Mon Sep 17 00:00:00 2001
+From 3a35e3920d9cef1086d4db1b7b3d14b641df92c5 Mon Sep 17 00:00:00 2001
 From: Peter Zijlstra <[email protected]>
 Date: Thu, 23 Mar 2017 15:56:10 +0100
-Subject: [PATCH 008/352] rtmutex: Clean up
+Subject: [PATCH 008/364] rtmutex: Clean up
 
 Upstream commit aa2bfe55366552cb7e93e8709d66e698d79ccc47
 

rt-patches/0009-sched-rtmutex-Refactor-rt_mutex_setprio.patch

@@ -1,7 +1,7 @@
-From c048650270917ece2cbfacb236e15c5a2808f36e Mon Sep 17 00:00:00 2001
+From 0c85c6a8dbe6acff73c7253d77024a525498cf2b Mon Sep 17 00:00:00 2001
 From: Peter Zijlstra <[email protected]>
 Date: Thu, 23 Mar 2017 15:56:11 +0100
-Subject: [PATCH 009/352] sched/rtmutex: Refactor rt_mutex_setprio()
+Subject: [PATCH 009/364] sched/rtmutex: Refactor rt_mutex_setprio()
 
 Upstream commit acd58620e415aee4a43a808d7d2fd87259ee0001
 
@@ -18,7 +18,7 @@ priority didn't change, this could lead to a stale pointer.
 As for the XXX, I think its fine to use pi_task->prio, because if it
 differs from waiter->prio, a PI chain update is immenent.
 
-Change-Id: I084a4779012628235f4bcb58697b4d0fa8c24371
+Change-Id: Icae7d14da4e0012007a05fa059bb8e9c897bf013
 Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
 Cc: [email protected]
 Cc: [email protected]
@@ -270,10 +270,10 @@ index 8801d2b..155d6cd 100644
 
  	return true; /* call rt_mutex_postunlock() */
 diff --git a/kernel/sched/core.c b/kernel/sched/core.c
-index 0545760..ced7866 100644
+index b057aba..4db255a 100644
 --- a/kernel/sched/core.c
 +++ b/kernel/sched/core.c
-@@ -3754,10 +3754,25 @@ EXPORT_SYMBOL(default_wake_function);
+@@ -3747,10 +3747,25 @@ EXPORT_SYMBOL(default_wake_function);
 
  #ifdef CONFIG_RT_MUTEXES
 
@@ -301,7 +301,7 @@ index 0545760..ced7866 100644
   *
   * This function changes the 'effective' priority of a task. It does
   * not touch ->normal_prio like __setscheduler().
-@@ -3765,17 +3780,41 @@ EXPORT_SYMBOL(default_wake_function);
+@@ -3758,17 +3773,41 @@ EXPORT_SYMBOL(default_wake_function);
   * Used by the rt_mutex code to implement priority inheritance
   * logic. Call site only calls if the priority of the task changed.
   */
@@ -346,7 +346,7 @@ index 0545760..ced7866 100644
 
  	/*
  	 * Idle task boosting is a nono in general. There is one
-@@ -3795,9 +3834,7 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
+@@ -3788,9 +3827,7 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
  		goto out_unlock;
  	}
 
@@ -357,15 +357,15 @@ index 0545760..ced7866 100644
  	oldprio = p->prio;
 
  	if (oldprio == prio)
-@@ -3821,7 +3858,6 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
+@@ -3814,7 +3851,6 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
  	 *          running task
  	 */
  	if (dl_prio(prio)) {
 -		struct task_struct *pi_task = rt_mutex_get_top_task(p);
  		if (!dl_prio(p->normal_prio) ||
  		    (pi_task && dl_prio(pi_task->prio) &&
  		     dl_entity_preempt(&pi_task->dl, &p->dl))) {
-@@ -3859,6 +3895,11 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
+@@ -3852,6 +3888,11 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
  	balance_callback(rq);
  	preempt_enable();
  }
@@ -377,7 +377,7 @@ index 0545760..ced7866 100644
  #endif
 
  void set_user_nice(struct task_struct *p, long nice)
-@@ -4106,10 +4147,9 @@ static void __setscheduler(struct rq *rq, struct task_struct *p,
+@@ -4099,10 +4140,9 @@ static void __setscheduler(struct rq *rq, struct task_struct *p,
  	 * Keep a potential priority boosting if called from
  	 * sched_setscheduler().
  	 */
@@ -390,7 +390,7 @@ index 0545760..ced7866 100644
 
  	if (dl_prio(p->prio))
  		p->sched_class = &dl_sched_class;
-@@ -4397,7 +4437,7 @@ static int __sched_setscheduler(struct task_struct *p,
+@@ -4390,7 +4430,7 @@ static int __sched_setscheduler(struct task_struct *p,
  		 * the runqueue. This will be done when the task deboost
  		 * itself.
  		 */

rt-patches/0010-sched-tracing-Update-trace_sched_pi_setprio.patch

@@ -1,7 +1,7 @@
-From 4c59685de7e8a5191a4c43096a3c97e4c194e538 Mon Sep 17 00:00:00 2001
+From d4d5c8f55043906b981075281e1e6b56e7f46734 Mon Sep 17 00:00:00 2001
 From: Peter Zijlstra <[email protected]>
 Date: Thu, 23 Mar 2017 15:56:12 +0100
-Subject: [PATCH 010/352] sched,tracing: Update trace_sched_pi_setprio()
+Subject: [PATCH 010/364] sched,tracing: Update trace_sched_pi_setprio()
 
 Upstream commit b91473ff6e979c0028f02f90e40c844959c736d8
 
@@ -99,10 +99,10 @@ index 5660b43..9fb7702 100644
 
  	TP_printk("comm=%s pid=%d oldprio=%d newprio=%d",
 diff --git a/kernel/sched/core.c b/kernel/sched/core.c
-index ced7866..37d2686 100644
+index 4db255a..d0b027c 100644
 --- a/kernel/sched/core.c
 +++ b/kernel/sched/core.c
-@@ -3834,7 +3834,7 @@ void rt_mutex_setprio(struct task_struct *p, struct task_struct *pi_task)
+@@ -3827,7 +3827,7 @@ void rt_mutex_setprio(struct task_struct *p, struct task_struct *pi_task)
  		goto out_unlock;
  	}
 

rt-patches/0011-rtmutex-Fix-more-prio-comparisons.patch

@@ -1,7 +1,7 @@
-From dcc6dc525324ba59e089df2e65ec0139db27a056 Mon Sep 17 00:00:00 2001
+From 737d435eada0eb7754637ecc156308b12d4e1982 Mon Sep 17 00:00:00 2001
 From: Peter Zijlstra <[email protected]>
 Date: Thu, 23 Mar 2017 15:56:14 +0100
-Subject: [PATCH 011/352] rtmutex: Fix more prio comparisons
+Subject: [PATCH 011/364] rtmutex: Fix more prio comparisons
 
 Upstream commit 19830e55247cddb3f46f1bf60b8e245593491bea
 

rt-patches/0012-rtmutex-Plug-preempt-count-leak-in-rt_mutex_futex_un.patch

@@ -1,7 +1,7 @@
-From 11b18ea9f507c0976869f8d0ca18be4cc9bdfd18 Mon Sep 17 00:00:00 2001
+From 3452e21d0f17a2c3aea4ebb77cdea51b52483f3e Mon Sep 17 00:00:00 2001
 From: Mike Galbraith <[email protected]>
 Date: Wed, 5 Apr 2017 10:08:27 +0200
-Subject: [PATCH 012/352] rtmutex: Plug preempt count leak in
+Subject: [PATCH 012/364] rtmutex: Plug preempt count leak in
  rt_mutex_futex_unlock()
 
 Upstream commit def34eaae5ce04b324e48e1bfac873091d945213

rt-patches/0013-futex-Fix-small-and-harmless-looking-inconsistencies.patch

@@ -1,7 +1,7 @@
-From 50e9bcab05ac6dc980423b250cef971c3452930f Mon Sep 17 00:00:00 2001
+From a088ac3819870a9113a7e7c26c56fdbfe657921a Mon Sep 17 00:00:00 2001
 From: Peter Zijlstra <[email protected]>
 Date: Fri, 7 Apr 2017 09:04:07 +0200
-Subject: [PATCH 013/352] futex: Fix small (and harmless looking)
+Subject: [PATCH 013/364] futex: Fix small (and harmless looking)
  inconsistencies
 
 Upstream commit 94ffac5d847cfd790bb37b7cef1cad803743985e

rt-patches/0014-futex-Clarify-mark_wake_futex-memory-barrier-usage.patch

@@ -1,7 +1,7 @@
-From d567be405a364bc6fb25632bd3a33e13cf6fca20 Mon Sep 17 00:00:00 2001
+From c2766def8487a0dc38b027bd295ef7447447da23 Mon Sep 17 00:00:00 2001
 From: "Darren Hart (VMware)" <[email protected]>
 Date: Fri, 14 Apr 2017 15:31:38 -0700
-Subject: [PATCH 014/352] futex: Clarify mark_wake_futex memory barrier usage
+Subject: [PATCH 014/364] futex: Clarify mark_wake_futex memory barrier usage
 
 Upstream commit 38fcd06e9b7f6855db1f3ebac5e18b8fdb467ffd
 

rt-patches/0015-MAINTAINERS-Add-FUTEX-SUBSYSTEM.patch

@@ -1,7 +1,7 @@
-From fa7593f014e90cfcf928817ff46e1708ddaf3fce Mon Sep 17 00:00:00 2001
+From 3f57286237a6206d9e3c1cf6c419152098dbbc96 Mon Sep 17 00:00:00 2001
 From: "Darren Hart (VMware)" <[email protected]>
 Date: Fri, 14 Apr 2017 15:46:08 -0700
-Subject: [PATCH 015/352] MAINTAINERS: Add FUTEX SUBSYSTEM
+Subject: [PATCH 015/364] MAINTAINERS: Add FUTEX SUBSYSTEM
 
 Upstream commit 59cd42c29618c45cd3c56da43402b14f611888dd
 
@@ -23,7 +23,7 @@ Signed-off-by: Thomas Gleixner <[email protected]>
  1 file changed, 17 insertions(+)
 
 diff --git a/MAINTAINERS b/MAINTAINERS
-index beb51ae..7e24caa 100644
+index c3cd026..05f00f4 100644
 --- a/MAINTAINERS
 +++ b/MAINTAINERS
 @@ -5196,6 +5196,23 @@ F:	fs/fuse/

rt-patches/0016-arm-at91-do-not-disable-enable-clocks-in-a-row.patch

@@ -1,7 +1,7 @@
-From 0d60e2f37b78604989bd555be6f352db6804b637 Mon Sep 17 00:00:00 2001
+From a7fb817f450a9d5ab14907898f76a12855b55ef6 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <[email protected]>
 Date: Wed, 9 Mar 2016 10:51:06 +0100
-Subject: [PATCH 016/352] arm: at91: do not disable/enable clocks in a row
+Subject: [PATCH 016/364] arm: at91: do not disable/enable clocks in a row
 
 Currently the driver will disable the clock and enable it one line later
 if it is switching from periodic mode into one shot.

rt-patches/0017-ARM-smp-Move-clear_tasks_mm_cpumask-call-to-__cpu_di.patch

@@ -1,7 +1,7 @@
-From 3f7e1dde27c2e18b8b904cc336c2b58d6790f3a6 Mon Sep 17 00:00:00 2001
+From 7b47876b7b40bdf88846c0d746eca1c9732a3dc5 Mon Sep 17 00:00:00 2001
 From: Grygorii Strashko <[email protected]>
 Date: Fri, 11 Sep 2015 21:21:23 +0300
-Subject: [PATCH 017/352] ARM: smp: Move clear_tasks_mm_cpumask() call to
+Subject: [PATCH 017/364] ARM: smp: Move clear_tasks_mm_cpumask() call to
  __cpu_die()
 
 When running with the RT-kernel (4.1.5-rt5) on TI OMAP dra7-evm and trying

rt-patches/0018-rtmutex-Handle-non-enqueued-waiters-gracefully.patch

@@ -1,7 +1,7 @@
-From c8dbe5248ddfc6f97e57a1e08fb8e4d033251e50 Mon Sep 17 00:00:00 2001
+From 1fb1883f795e8e581a56b4342184f446196c3472 Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <[email protected]>
 Date: Fri, 6 Nov 2015 18:51:03 +0100
-Subject: [PATCH 018/352] rtmutex: Handle non enqueued waiters gracefully
+Subject: [PATCH 018/364] rtmutex: Handle non enqueued waiters gracefully
 
 Yimin debugged that in case of a PI wakeup in progress when
 rt_mutex_start_proxy_lock() calls task_blocks_on_rt_mutex() the latter

rt-patches/0019-fs-dcache-include-wait.h.patch

@@ -1,7 +1,7 @@
-From 0dd5f2cf639eb8f0062f61cc04c1dba095cd6e45 Mon Sep 17 00:00:00 2001
+From 43f0f8744365f23083dbbb0b4be185cc77296314 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <[email protected]>
 Date: Wed, 14 Sep 2016 11:55:23 +0200
-Subject: [PATCH 019/352] fs/dcache: include wait.h
+Subject: [PATCH 019/364] fs/dcache: include wait.h
 
 Since commit d9171b934526 ("parallel lookups machinery, part 4 (and
 last)") dcache.h is using but does not include wait.h. It works as long

rt-patches/0020-rbtree-include-rcu.h-because-we-use-it.patch

@@ -1,7 +1,7 @@
-From 516f0efce4354e1aa258cdfe1cfba6876f6f3c97 Mon Sep 17 00:00:00 2001
+From 4ec9fe53318efbd941937adffbde8d70a0b213ec Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <[email protected]>
 Date: Wed, 14 Sep 2016 11:52:17 +0200
-Subject: [PATCH 020/352] rbtree: include rcu.h because we use it
+Subject: [PATCH 020/364] rbtree: include rcu.h because we use it
 
 Since commit c1adf20052d8 ("Introduce rb_replace_node_rcu()")
 rbtree_augmented.h uses RCU related data structures but does not include

rt-patches/0021-fs-dcache-init-in_lookup_hashtable.patch

@@ -1,7 +1,7 @@
-From b8228afc54efeee2253d35f5d6faeb37d75ac502 Mon Sep 17 00:00:00 2001
+From 07d504f0c5d0c20d1063e24e7d970b2f4e382c01 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <[email protected]>
 Date: Wed, 14 Sep 2016 17:57:03 +0200
-Subject: [PATCH 021/352] fs/dcache: init in_lookup_hashtable
+Subject: [PATCH 021/364] fs/dcache: init in_lookup_hashtable
 
 in_lookup_hashtable was introduced in commit 94bdd655caba ("parallel
 lookups machinery, part 3") and never initialized but since it is in

rt-patches/0022-iommu-vt-d-don-t-disable-preemption-while-accessing-.patch → rt-patches/0023-iommu-vt-d-don-t-disable-preemption-while-accessing-.patch

@@ -1,7 +1,7 @@
-From c8680b9688e6f9c2f120d3a4e95d36d142e584a8 Mon Sep 17 00:00:00 2001
+From 79d0803f627d806e4b7bfd44327b34f027608a26 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <[email protected]>
 Date: Thu, 15 Sep 2016 17:16:44 +0200
-Subject: [PATCH 022/352] iommu/vt-d: don't disable preemption while accessing
+Subject: [PATCH 023/364] iommu/vt-d: don't disable preemption while accessing
  deferred_flush()
 
 get_cpu() disables preemption and returns the current CPU number. The