On Thu, 2026-05-07 at 10:09 -0700, Paul E. McKenney wrote: > It turns out that there are BPF use cases that rely on nesting RCU > Tasks Trace readers. These use cases are well-served by the old > rcu_read_lock_trace() and rcu_read_unlock_trace() functions that maintain > a nesting counter in the task_struct structure. But these use cases incur > a performance penalty when using the shiny new rcu_read_lock_tasks_trace() > and rcu_read_unlock_tasks_trace() functions, which nest in the same way > that SRCU does. > > This means that rcu_read_lock_trace() and rcu_read_unlock_trace() > will be with us for some time. Therefore, remove the checkpatch.pl > deprecation.
Fine by me. Perhaps combining patches 3 and 4 would be more intelligible.
