Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5154460pxj; Tue, 22 Jun 2021 16:42:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw2cH5yv5rNNSs87YZl6hHYBqOE/fy53wCw+d1ODQNR26Y7yQHcugM/Vuf1YOOyCYVbNPfj X-Received: by 2002:a05:6e02:10c3:: with SMTP id s3mr785092ilj.37.1624405372047; Tue, 22 Jun 2021 16:42:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624405372; cv=none; d=google.com; s=arc-20160816; b=qjq8UU8dM+5PwM6dXR3roHUaKKWu8WNx47rjoh/fYVY/gWjI2/pP0h699tnt6CmMIg WqkrLSGo3a8HyRhGUkuoKL62VaT1ktuEg7kR+nxte1OJbWGtliJq1CuUjT5zkHoxyz/5 W0DhYWOfT3Zu59DgqYGiTRJoV3beSXGvzf4ysW5GXr7a/MwoqYUo5FZuTr8JpP3cLWJP WjfY0Yc9hVSr7DtnMgyrlMafObm/uFBtN8quyC3vE1RvkP0QIuN2b+l1AxsLcWki8zK5 SXif1WIdgZWbC7vqALAl6vPoDDRiki3+OhUvAe5LQwvWioGWAkDHQSGoeLrD0n4Op7HS 5qrQ== 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=7MSw2/IpZeD3ZyNGEdop52TR/Is/v6NrH7IRIVKxd7M=; b=tMYZzsHaPwOrBBNJ0iONu0xbMo+/Torw38BWmXvsAwsycwI8Y0Mk6cgqw2HgnjGJN3 6L0weFS4Hmnqr6MkgvjCea3HtX4NhGam9OwqClrjsXOC1M1GX5NTIKsURfaa4ensXB4u 3SxNS4xSJ+thMzJL8pYCXLXrSpQBlxQ+hxqgITb1wHA1me0rKw6ibE5BzAUG7fdWOKGb TS68Xi7IKTiQpNNyMh0XHn3rUuXTPQga3c9cF3AYkwfIUdX5bHm8FJofjzggo1mXcYK/ 1C7Yanp7hZjoYspnfTQoq11IN5daglURbp8RmBzyvBaWl9P65GYZPbbtFOzNBS2g3UJq GZPw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=APtIlBGB; 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 14si5708524ilx.147.2021.06.22.16.42.40; Tue, 22 Jun 2021 16:42:52 -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=APtIlBGB; 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 S229907AbhFVXoV (ORCPT + 99 others); Tue, 22 Jun 2021 19:44:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:52536 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229747AbhFVXoV (ORCPT ); Tue, 22 Jun 2021 19:44:21 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 69FAE61003; Tue, 22 Jun 2021 23:42:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1624405325; bh=g4E/vdYh2QVf8t933gHLgeNZUvOXHmnn6xmrpWfhGlg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=APtIlBGBprpAh3N1sTE4nJF6xqWCbAJPKeWDs+FZUdRYU8Cy9ATCMHKVfsN8eQVjB pK+739hYzMIKv1E01/8k76+UlbSDMQB/Nv3reKUih0ZOvVluVIduoyTbKER2SClBWy dTt03/z2a1AKeU222AUaz9zhA16va/Nhd2odZtK0g1GRXjhy/EPFqE9b2szSIH5uk5 EK6JF4ezksMloHCeic8BZWvNpLJWqNy2wjphohvTdlzH+T5vRSjJ5vdWknzx5tErc+ Yvdy63pRe4LY+qhpzLjz9RnYHtPlCNP9KsWywDKOlP3meX8mzatF7sb44AUtfIn/j4 /fvAKfkW6MxmQ== From: Frederic Weisbecker To: Thomas Gleixner , Peter Zijlstra Cc: LKML , Frederic Weisbecker , "Eric W . Biederman" , Oleg Nesterov , stable@vger.kernel.org, Ingo Molnar Subject: [PATCH 1/7] posix-cpu-timers: Fix rearm racing against process tick Date: Wed, 23 Jun 2021 01:41:49 +0200 Message-Id: <20210622234155.119685-2-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 Since the process wide cputime counter is started locklessly from posix_cpu_timer_rearm(), it can be concurrently stopped by operations on other timers from the same thread group, such as in the following unlucky scenario: CPU 0 CPU 1 ----- ----- timer_settime(TIMER B) posix_cpu_timer_rearm(TIMER A) cpu_clock_sample_group() (pct->timers_active already true) handle_posix_cpu_timers() check_process_timers() stop_process_timers() pct->timers_active = false arm_timer(TIMER A) tick -> run_posix_cpu_timers() // sees !pct->timers_active, ignore // our TIMER A Fix this with simply locking process wide cputime counting start and timer arm in the same block. Acked-by: Peter Zijlstra (Intel) Signed-off-by: Frederic Weisbecker Fixes: 60f2ceaa8111 ("posix-cpu-timers: Remove unnecessary locking around cpu_clock_sample_group") Cc: stable@vger.kernel.org Cc: Oleg Nesterov Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Eric W. Biederman --- kernel/time/posix-cpu-timers.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/kernel/time/posix-cpu-timers.c b/kernel/time/posix-cpu-timers.c index 3bb96a8b49c9..aa52fc85dbcb 100644 --- a/kernel/time/posix-cpu-timers.c +++ b/kernel/time/posix-cpu-timers.c @@ -991,6 +991,11 @@ static void posix_cpu_timer_rearm(struct k_itimer *timer) if (!p) goto out; + /* Protect timer list r/w in arm_timer() */ + sighand = lock_task_sighand(p, &flags); + if (unlikely(sighand == NULL)) + goto out; + /* * Fetch the current sample and update the timer's expiry time. */ @@ -1001,11 +1006,6 @@ static void posix_cpu_timer_rearm(struct k_itimer *timer) bump_cpu_timer(timer, now); - /* Protect timer list r/w in arm_timer() */ - sighand = lock_task_sighand(p, &flags); - if (unlikely(sighand == NULL)) - goto out; - /* * Now re-arm for the new expiry time. */ -- 2.25.1