summaryrefslogtreecommitdiff
path: root/kernel/time
diff options
context:
space:
mode:
authorShakeel Butt <shakeel.butt@linux.dev>2026-10-10 12:15:00 -0700
committerPeter Zijlstra <peterz@infradead.org>2026-10-16 09:49:03 +0200
commit6f88f6cbb0472a8481ba560578a1d7c8d802eba7 (patch)
treeabfd4f012fcf3f5947d72142871599b020ab0850 /kernel/time
parentb0f1d7a34d3099973f1ba45d1ce6f36578e510a2 (diff)
sched/psi: Remove the RCU wait from trigger destruction
In the Meta fleet, we found PSI trigger destruction waiting for an RCU grace period while holding kernfs node_mutex, blocking other users [1]. File close and node drain hold this mutex while calling the release callback. Cgroup removal and disabling cgroup.pressure also hold cgroup_mutex during the drain. The wait was added by commit 0e94682b73bf ("psi: introduce psi monitor") to protect worker and trigger lookups. Commit 461daba06bdc ("psi: eliminate kthread_worker from psi trigger scheduling mechanism") replaced the worker queue with a group timer. The scheduler now only checks whether rtpoll_task is NULL; it uses neither the task nor the trigger. Commit a06247c6804f ("psi: Fix uaf issue when psi trigger is destroyed while being polled") removed trigger replacement and polling's RCU lookup. Trigger lists are protected by mutexes. Proc poll/select entries are removed before their file references are dropped. eventpoll_release() removes epoll entries before the file release callback. Commit aff037078eca ("sched/psi: use kernfs polling functions for PSI trigger polling") moved cgroup polling to a kernfs waitqueue whose lifetime follows the file. A late timer firing only wakes the group waitqueue. The system group is static, and commit 5457025fa8ca ("sched/psi: Shut down rtpoll_timer in psi_cgroup_free()") shuts down the cgroup timer before freeing the group. Cgroup reclamation already waits for scheduler readers. Remove synchronize_rcu() from psi_trigger_destroy() and use rcu_access_pointer() for the worker NULL check. Keep kthread_stop() outside the trigger mutex. Tested trigger churn, notifications and cgroup removal in an 8-CPU VM with KASAN, lockdep, and full and lazy preemption. No warnings were found. Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Acked-by: Tejun Heo <tj@kernel.org> Link: https://github.com/bpftrace/user-tools/tree/master/runnablelockmonitor [1] Link: https://patch.msgid.link/20261010191500.3895736-1-shakeel.butt@linux.dev
Diffstat (limited to 'kernel/time')
0 files changed, 0 insertions, 0 deletions