From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794047196; b=U2kDxbbyhdGCqhj7AHipP4kt5m2ypfq1m+bHC4Aegdu19wy6dITwQwDD7oaAkvyYveVW US2kofrHaPOpC2irR8mMvFk9CdFNQZ1mA/9SjvLeCdhb22z5+sF3CUEJrXJRCad+l80O1 SKpKUk4yaUDF2eXHiPIzoghtGxZC2Vi1BjKbfJyRCn+lcXhOdngsClcljVhQLxKBjrphi 8RfqDihb7gg7s5bREHup4DMod5TP5a/9yf8o90f9wIFhi+YZVahCXLlKUmUQ1oZ8vF9/C B6XqXxLw3b4Osn2f7GmIAteFMsGIOFglBns6jHtccEfnTnP7IIRbbudTRg/Nw78pqsg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794047196; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=9t6yr9NjbsQA8U6cf+1NJg05xhF5StG/XGmZPDBy6cc=; b=z3VJ4Id88sHxcCh+4Af2+r2mb+ymGlg+9ZZ62hz6/IgIHvl5wPVyKNs6Irhg01YhXX7D RBKuCP1tReof/+U46gJ7b0NkAoo+2ndh1CKGOWFWRDxbrsa4eBulIKOAZGdXzQREEATpJ oDIDn0gQjtaoGic2G40hZTOsEXmc6Zf4X8KgMVWDbP2wpoWgaQtk7dSerkWT83qqRnZF7 GvOvd/jTeK70XowkvSZMgATczVxp0LaCM0ZyyH6ftxuNoyFszEKYrECmEBT6kLA+qb2Rg VUobmnUjCSDbaRt7FA5CwfbcULgT9vgp+c4FlHzwDUyLaGDmLUMy7aELHGtksYNy81w== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=Ee4MCNAG; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1CD31606A330 for ; Sat, 7 Nov 2026 10:26:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=Ee4MCNAG Received: by smtp.kernel.org (Postfix) with ESMTPSA id 27C551F0089F; Sat, 7 Nov 2026 10:26:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794047195; bh=9t6yr9NjbsQA8U6cf+1NJg05xhF5StG/XGmZPDBy6cc=; h=From:To:Cc:Subject:Date; b=Ee4MCNAGzA5ye1UxvgAXv7ESPfIX/2NKutxOHFpB9y2HpWF5j1bWZ8wLjXEWgya/k aiyHJ/Wcug3Uo+2aMvZDvoRl7F8Cv/VBXL/AniPJKWqXTAdr77BopekR2Pk9My3mvp 2tWVToBHQ56KDnYFvz9tdsqMMbjyQ1tsgy5ao15WYaOwPuiy56LXwj/UDGKnUiimug P2ec41NTtE5NFg5g+5l0XlXaRvmydxbGRDgACUtddRXaKDXGuYKdz7HFryK+iK2okM 0PmXB+FzOw27I3eaRByAXqrclk7zNYShupaSQAhNThmatr/Up21SzmZQtgC72DxE9V +pU+eA2Xvgtgw== From: Sasha Levin To: peng_wang@linux.alibaba.com, frederic@kernel.org, herongguang@linux.alibaba.com, tglx@kernel.org Cc: stable@vger.kernel.org Subject: FAILED: patch "[PATCH] tick/nohz: Reevaluate the tick for kicks flushed outside hardirq" failed to apply to 6.12-stable tree Date: Sat, 7 Nov 2026 05:26:34 -0500 Message-ID: <20261107052634-failed-6.12-e389ae428847@kernel.org> X-Mailer: git-send-email 2.53.0 X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The patch below does not apply to the 6.12-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.12.y git checkout FETCH_HEAD git cherry-pick -x e389ae428847a2e6a3b698b5967df68ccf90361c # git commit -s git send-email --to '' --in-reply-to '20261107052634-failed-6.12-e389ae428847@kernel.org' --subject-prefix 'PATCH 6.12.y' 'HEAD^..' Thanks, Sasha ------------------ original commit in Linus's tree ------------------ >From e389ae428847a2e6a3b698b5967df68ccf90361c Mon Sep 17 00:00:00 2001 From: Peng Wang Date: Fri, 23 Oct 2026 22:51:00 +0800 Subject: [PATCH] tick/nohz: Reevaluate the tick for kicks flushed outside hardirq The nohz full kick relies on interrupt exit to reevaluate the tick. However, a remote kick can also be flushed from task context without an interrupt exit guaranteed to follow. If a tick dependency is set or an earlier timer is queued after the idle-exit reevaluation, the required tick update can be delayed until another interrupt. Reevaluate the tick directly from the callback outside hardirq context. Keep the existing interrupt exit handling for hardirq callbacks. The offline flush remains harmless because tick_sched_timer_dying() has already cleared TS_FLAG_NOHZ. Fixes: 4b44a21dd640 ("irq_work, smp: Allow irq_work on call_single_queue") Fixes: a5183862e76f ("tick/nohz: Conditionally restart tick on idle exit") Suggested-by: Frederic Weisbecker Co-developed-by: He Rongguang Signed-off-by: He Rongguang Signed-off-by: Peng Wang Signed-off-by: Thomas Gleixner Reviewed-by: Frederic Weisbecker Cc: stable@vger.kernel.org Link: https://patch.msgid.link/20261023145101.8217-1-peng_wang@linux.alibaba.com --- kernel/time/tick-sched.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c index 6c3fea3867139..baa3ac9b48f88 100644 --- a/kernel/time/tick-sched.c +++ b/kernel/time/tick-sched.c @@ -400,9 +400,21 @@ static bool can_stop_full_tick(int cpu, struct tick_sched *ts) return true; } +static void tick_nohz_full_update_tick(struct tick_sched *ts); + static void nohz_full_kick_func(struct irq_work *work) { - /* Empty, the tick restart happens on tick_nohz_irq_exit() */ + struct tick_sched *ts = this_cpu_ptr(&tick_cpu_sched); + + if (WARN_ON_ONCE(!tick_nohz_full_cpu(smp_processor_id()))) + return; + + /* Task-context flushes may not be followed by an IRQ exit. */ + if (!in_hardirq()) { + if (WARN_ON_ONCE(tick_sched_flag_test(ts, TS_FLAG_INIDLE))) + return; + tick_nohz_full_update_tick(ts); + } } static DEFINE_PER_CPU(struct irq_work, nohz_full_kick_work) = -- 2.53.0