Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5154638pxj; Tue, 22 Jun 2021 16:43:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyuJ5TY+vUNP2S6HHvo/IQUCwiefm/2oh5E6X0VDWRiNkCckOGIjpvV1L9tjMs7kzumzH8S X-Received: by 2002:a5d:9414:: with SMTP id v20mr4922533ion.66.1624405390539; Tue, 22 Jun 2021 16:43:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624405390; cv=none; d=google.com; s=arc-20160816; b=vlF08XTEpi06J+Ur6jIPAGRfBLozB0Y0AUnn8vRBIU+UKyeuv+i6qQYEksMhHEDzb8 x6BsolZWVd6KpjWsqZMTdFFtzwER1rYxejKEgP3WsXcnrKrnhjWA6RMuoea3ryzkG7qE v7OIe38KYmkHW7s8QLCB+j/iLLolaELm5moak4jjSJnSLaGdIUL8NKIsbojarkpe7TtW 2B/7TY/mf+8pZrzyaAecco5yiZACfsdMZqYOUegxqn3UlNqyamZ37Bc5eFkwxZ9PoWZl 5F4RQxdDBD4CObEvTnBGr7moYS8AVKRliQS/4AF4hoYzaWoBagmF0FlMpzWJnV0rnvb4 roGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=ar14FN5p3yvc5Y4JCBlLlYF6GpccRy9qIXmRDnSpvZ4=; b=BBBnq5xpMKFfMZOIBCcEo13nloBx1vBEa3nvedIvgS07mHdAtGYWVNlLgWKKFYgDgg Ae8cf3E1HRHyU5L49Iro/Z/LjYzt3ZUnQ1NX609XRE99EZ0jOqV3UWzaGYIxgvt053dM 7JXl3qlyjPSVfFI1mScqsE+bXSDdxSrMVB2mUYo2xpgVjsLR3lJa1NWAYRpt5SztNG0i OtAmp26zKXQh3IOKv0szaoqeC+21EisRHj/zpCLABtRX7S+n9JHetBBZ9yCYHmy4p+VF ShvpDCfG/GrwezKPAoIAFrBDqzYQRjxSO8iaQFievGK2rsuZNfCkmwN2sS2MhHL4E2Yt Iz2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=owdMhLV8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c9si19202481ilu.72.2021.06.22.16.42.58; Tue, 22 Jun 2021 16:43:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=owdMhLV8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230002AbhFVXo1 (ORCPT + 99 others); Tue, 22 Jun 2021 19:44:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:52730 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229747AbhFVXo1 (ORCPT ); Tue, 22 Jun 2021 19:44:27 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 3F4756135A; Tue, 22 Jun 2021 23:42:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1624405330; bh=Pp7IXW9CuTZ/eAAexklW/FU0iA9vx3eezutjba+V8js=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=owdMhLV8JBllX74HI2RPdjnCKx1vh9k0Jy2wUlIkS7gNDdubmC6Q0Dhfj8MM+LIqf kFBJcTMOM6s3MrdvHSxUL/uCDo1WHNbNbii6Z+FU9MDZwLRMCLgE20lo38h5zK8RU8 89in7GR7Jzv2ZOXQqF88760iucrw71FdOpxsWy4/h7UggErudcjfevgmATB5sRa+py 7oytwJoyH424RWbtkXMdjB1SM1bKmYYib7lMND0ad/VprEOE3H0XT8wKbNmaMj0kX6 PZJeR20NHKAWsNEqZbgP9SRpSCqnV+bg9IlaXXllFmkhCIFDQPADg2oDMPATel1JcQ XcAtW2vici6rw== From: Frederic Weisbecker To: Thomas Gleixner , Peter Zijlstra Cc: LKML , Frederic Weisbecker , "Eric W . Biederman" , Oleg Nesterov , Ingo Molnar Subject: [PATCH 4/7] posix-cpu-timers: Force next expiration recalc after itimer reset Date: Wed, 23 Jun 2021 01:41:52 +0200 Message-Id: <20210622234155.119685-5-frederic@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20210622234155.119685-1-frederic@kernel.org> References: <20210622234155.119685-1-frederic@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 we reach 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 Cc: Oleg Nesterov Cc: Thomas Gleixner Cc: Peter Zijlstra (Intel) Cc: Ingo Molnar Cc: Eric W. Biederman --- 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 13939f47c7b0..cc9f8be67694 100644 --- a/kernel/time/posix-cpu-timers.c +++ b/kernel/time/posix-cpu-timers.c @@ -1379,8 +1379,6 @@ void set_process_cpu_timer(struct task_struct *tsk, unsigned int clkid, } } - if (!*newval) - return; *newval += now; } -- 2.25.1