diff options
| author | Frederic Weisbecker | 2022-11-25 14:54:59 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman | 2023-03-10 09:32:51 +0100 |
| commit | 24f259ce3a7c8951f80c874c6193a8f8de139c22 (patch) | |
| tree | 773cbfaba670970a5ed94ade64a812eac9813635 /fs/crypto | |
| parent | a2b0cda452b78d96c28d0ee984f1d0ede23b1948 (diff) | |
rcu-tasks: Remove preemption disablement around srcu_read_[un]lock() calls
[ Upstream commit 44757092958bdd749775022f915b7ac974384c2a ]
Ever since the following commit:
5a41344a3d83 ("srcu: Simplify __srcu_read_unlock() via this_cpu_dec()")
SRCU doesn't rely anymore on preemption to be disabled in order to
modify the per-CPU counter. And even then it used to be done from the API
itself.
Therefore and after checking further, it appears to be safe to remove
the preemption disablement around __srcu_read_[un]lock() in
exit_tasks_rcu_start() and exit_tasks_rcu_finish()
Suggested-by: Boqun Feng <boqun.feng@gmail.com>
Suggested-by: Paul E. McKenney <paulmck@kernel.org>
Suggested-by: Neeraj Upadhyay <quic_neeraju@quicinc.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Stable-dep-of: 28319d6dc5e2 ("rcu-tasks: Fix synchronize_rcu_tasks() VS zap_pid_ns_processes()")
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/crypto')
0 files changed, 0 insertions, 0 deletions