From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Sasha Levin <sashal@kernel.org>
Subject: [PATCH AUTOSEL 4.14 05/17] posix-cpu-timers: Force next expiration recalc after itimer reset
Date: Sun, 5 Sep 2021 21:23:40 -0400 [thread overview]
Message-ID: <20210906012352.930954-5-sashal@kernel.org> (raw)
In-Reply-To: <20210906012352.930954-1-sashal@kernel.org>
From: Frederic Weisbecker <frederic@kernel.org>
[ 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>
---
kernel/time/posix-cpu-timers.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/time/posix-cpu-timers.c b/kernel/time/posix-cpu-timers.c
index fb5a57ffb98c..495d690cc92b 100644
--- a/kernel/time/posix-cpu-timers.c
+++ b/kernel/time/posix-cpu-timers.c
@@ -1207,8 +1207,6 @@ void set_process_cpu_timer(struct task_struct *tsk, unsigned int clock_idx,
}
}
- if (!*newval)
- return;
*newval += now;
}
--
2.30.2
next prev parent reply other threads:[~2021-09-06 1:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 1:23 [PATCH AUTOSEL 4.14 01/17] regmap: fix the offset of register error log Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 02/17] crypto: mxs-dcp - Check for DMA mapping errors Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 03/17] power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 04/17] crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop() Sasha Levin
2021-09-06 1:23 ` Sasha Levin [this message]
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 06/17] udf: Check LVID earlier Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 07/17] isofs: joliet: Fix iocharset=utf8 mount option Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 08/17] nvme-rdma: don't update queue count when failing to set io queues Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 09/17] power: supply: max17042_battery: fix typo in MAx17042_TOFF Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 10/17] s390/cio: add dev_busid sysfs entry for each subchannel Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 11/17] libata: fix ata_host_start() Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 12/17] crypto: qat - do not ignore errors from enable_vf2pf_comms() Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 13/17] crypto: qat - handle both source of interrupt in VF ISR Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 14/17] crypto: qat - fix reuse of completion variable Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 15/17] crypto: qat - fix naming for init/shutdown VF to PF notifications Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 16/17] crypto: qat - do not export adf_iov_putmsg() Sasha Levin
2021-09-06 1:23 ` [PATCH AUTOSEL 4.14 17/17] udf_get_extendedattr() had no boundary checks Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210906012352.930954-5-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox