Commit 7b2b55da authored by Jason Xing's avatar Jason Xing Committed by Linus Torvalds
Browse files

psi: get poll_work to run when calling poll syscall next time

Only when calling the poll syscall the first time can user receive
POLLPRI correctly.  After that, user always fails to acquire the event

Reproduce case:
 1. Get the monitor code in Documentation/accounting/psi.txt
 2. Run it, and wait for the event triggered.
 3. Kill and restart the process.

The question is why we can end up with poll_scheduled = 1 but the work
not running (which would reset it to 0).  And the answer is because the
scheduling side sees group->poll_kworker under RCU protection and then
schedules it, but here we cancel the work and destroy the worker.  The
cancel needs to pair with resetting the poll_scheduled flag.


Signed-off-by: default avatarJason Xing <>
Signed-off-by: default avatarJoseph Qi <>
Reviewed-by: default avatarCaspar Zhang <>
Reviewed-by: default avatarSuren Baghdasaryan <>
Acked-by: default avatarJohannes Weiner <>
Cc: Ingo Molnar <>
Cc: Peter Zijlstra <>
Cc: <>
Signed-off-by: default avatarAndrew Morton <>
Signed-off-by: default avatarLinus Torvalds <>
parent bb65f89b
......@@ -1131,7 +1131,15 @@ static void psi_trigger_destroy(struct kref *ref)
* deadlock while waiting for psi_poll_work to acquire trigger_lock
if (kworker_to_destroy) {
* After the RCU grace period has expired, the worker
* can no longer be found through group->poll_kworker.
* But it might have been already scheduled before
* that - deschedule it cleanly before destroying it.
atomic_set(&group->poll_scheduled, 0);
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment