From nobody Tue Dec 2 00:26:31 2025 Received: from cvsmtppost16.nm.naver.com (cvsmtppost16.nm.naver.com [114.111.35.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F14BAEAF9 for ; Tue, 25 Nov 2025 00:14:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=114.111.35.234 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764029669; cv=none; b=aqjwgtLYGhEpofrbpPsOLJiWjGVzy1WwOLd5fElccOQCchLe2HOHhZJvnqXEP09ye6Qwy/qCmikQzpXD0gISbFWYgzvyIBtBRGB87vDhwl5v7DA3cbotqNjCb88DTLQgjEUiBwU6hic+Qn4i6pVWQLHrkzETpwQUIRkm+bKwTG4= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764029669; c=relaxed/simple; bh=dIa2E1CMe2k67XSNWKEosIXOHQ5uREF+wrK39QTrNys=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=fZDK4/1RSpTM92AIK+MHOR+wKbQLXPifzslrHswz7EEoDw7D5pSfptorAMkDICqlA/oFXJpAAbGsOv3nBzJP38yTGu37nfXM8EC2InpH0J7ZkmRfcHG2eJyPECrJr+KuxAiE9DgzH/2ODhMK3WtPmtEIupFSJpjzL9b9nnnQ6Q4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=naver.com; spf=pass smtp.mailfrom=naver.com; dkim=pass (2048-bit key) header.d=naver.com header.i=@naver.com header.b=UlwJzoDE; arc=none smtp.client-ip=114.111.35.234 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=naver.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=naver.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=naver.com header.i=@naver.com header.b="UlwJzoDE" Received: from cvsendbo008.nm ([10.112.24.37]) by cvsmtppost16.nm.naver.com with ESMTP id WDiIlPTaSUKJyNUMPWcUjA for ; Tue, 25 Nov 2025 00:04:18 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=naver.com; s=s20171208; t=1764029058; bh=dIa2E1CMe2k67XSNWKEosIXOHQ5uREF+wrK39QTrNys=; h=From:To:Subject:Date:Message-ID:From:Subject:Feedback-ID: X-Works-Security; b=UlwJzoDEyE7MTbymyr0jnUcPXlcxF65KglCKFzKaxNaB2AOJd7xZyNEeJdIjVN0ir 5G3Qn2+RVCcBTqOFJ4qZgJSKN73g7qtO+sjR70ctIvqsp0dYCADxGQ0xq2mZlsqVy4 gYbURdXFjporvMlYUJ8KG7FEg0M8g77n5N32iNG9Fk4N2Ox5DrPkErUr9fF9DjdxLH wexmEPHq+4AilG1CqSZP7gtrfNZ6gT0Mlg7cwvmGYzRNu1TQ32kT69La1tdoQ7k0PA 30LJtbrF4okL8blpfLjjxcBVMy1/te8jjtw/Cc1ae6c+d59FxfKlpNmHHE4uz//fjq cPaHlwjpU9mAA== X-Session-ID: vY6KEOIMSDC-MMbcaVcGFQ X-Works-Send-Opt: xdYZjAJYjHmZaAKqKBmmKxbwKqpYkEljxBmwjAg= X-Works-Smtp-Source: A9KlaxKrFqJZ+HmXFxMr+6E= Received: from localhost.localdomain ([14.38.141.199]) by cvnsmtp005.nm.naver.com with ESMTP id vY6KEOIMSDC-MMbcaVcGFQ for (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Tue, 25 Nov 2025 00:04:17 -0000 From: Minu Jin To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, vincent.guittot@linaro.org, akpm@linux-foundation.org, david@kernel.org, kees@kernel.org Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de, vschneid@redhat.com, lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org, surenb@google.com, mhocko@suse.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Minu Jin Subject: [PATCH] fork-comment-fix: remove ambiguous question mark in CLONE_CHILD_CLEARTID comment Date: Tue, 25 Nov 2025 09:04:07 +0900 Message-ID: <20251125000407.24470-1-s9430939@naver.com> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The current comment "Clear TID on mm_release()?" ends with a question mark, implying uncertainty about whether the TID is actually cleared in mm_releas= e(). However, the code flow is deterministic. When a task exits, mm_release() explicitly checks 'tsk->clear_child_tid' an= d clears. Since this behavior is unambiguous, remove the confusing question mark and rephrase the comment to clearly stat= e that TID is cleared in mm_release(). Signed-off-by: Minu Jin --- kernel/fork.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/fork.c b/kernel/fork.c index 3da0f08615a9..ed46e12c8060 100644 --- a/kernel/fork.c +++ b/kernel/fork.c @@ -2031,7 +2031,7 @@ __latent_entropy struct task_struct *copy_process( =20 p->set_child_tid =3D (clone_flags & CLONE_CHILD_SETTID) ? args->child_tid= : NULL; /* - * Clear TID on mm_release()? + * TID is cleared in mm_release() when the task exits */ p->clear_child_tid =3D (clone_flags & CLONE_CHILD_CLEARTID) ? args->child= _tid : NULL; =20 --=20 2.43.0