aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/time/tick-internal.h
diff options
context:
space:
mode:
authorFrederic Weisbecker <frederic@kernel.org>2021-07-26 14:55:10 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-09-15 09:50:24 +0200
commit13ccaef77ee86047033c50bf59cb19e0dda3aa97 (patch)
tree3c9e7ae19be8361156150f1b86b32adf32e94317 /kernel/time/tick-internal.h
parent8a6c5eec811c1013001c8dc9874bf647b3c4ec36 (diff)
downloadkernel_replicant_linux-13ccaef77ee86047033c50bf59cb19e0dda3aa97.tar.gz
kernel_replicant_linux-13ccaef77ee86047033c50bf59cb19e0dda3aa97.tar.bz2
kernel_replicant_linux-13ccaef77ee86047033c50bf59cb19e0dda3aa97.zip
posix-cpu-timers: Force next expiration recalc after itimer reset
[ Upstream commit 406dd42bd1ba0c01babf9cde169bb319e52f6147 ] When an itimer deactivates a previously armed expiration, it simply doesn't do anything. As a result the process wide cputime counter keeps running and the tick dependency stays set until it reaches the old ghost expiration value. This can be reproduced with the following snippet: void trigger_process_counter(void) { struct itimerval n = {}; n.it_value.tv_sec = 100; setitimer(ITIMER_VIRTUAL, &n, NULL); n.it_value.tv_sec = 0; setitimer(ITIMER_VIRTUAL, &n, NULL); } Fix this with resetting the relevant base expiration. This is similar to disarming a timer. Signed-off-by: Frederic Weisbecker <frederic@kernel.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/20210726125513.271824-4-frederic@kernel.org Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'kernel/time/tick-internal.h')
0 files changed, 0 insertions, 0 deletions