[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241203095414.164750-2-costa.shul@redhat.com>
Date: Tue, 3 Dec 2024 11:54:13 +0200
From: Costa Shulyupin <costa.shul@...hat.com>
To: Waiman Long <longman@...hat.com>,
Tejun Heo <tj@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
Michal Koutný <mkoutny@...e.com>,
cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Costa Shulyupin <costa.shul@...hat.com>
Subject: [PATCH] cgroup/cpuset: Remove stale text
Paragraph "The task_lock() exception ...." was removed by
commit 2df167a300d7 ("cgroups: update comments in cpuset.c")
Remove stale text:
'See "The task_lock() exception", at the end of this comment.'
and reformat.
Signed-off-by: Costa Shulyupin <costa.shul@...hat.com>
---
kernel/cgroup/cpuset.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
index d5d2b4036314..c833a86f73ce 100644
--- a/kernel/cgroup/cpuset.c
+++ b/kernel/cgroup/cpuset.c
@@ -208,9 +208,8 @@ static struct cpuset top_cpuset = {
/*
* There are two global locks guarding cpuset structures - cpuset_mutex and
* callback_lock. We also require taking task_lock() when dereferencing a
- * task's cpuset pointer. See "The task_lock() exception", at the end of this
- * comment. The cpuset code uses only cpuset_mutex. Other kernel subsystems
- * can use cpuset_lock()/cpuset_unlock() to prevent change to cpuset
+ * task's cpuset pointer. The cpuset code uses only cpuset_mutex. Other kernel
+ * subsystems can use cpuset_lock()/cpuset_unlock() to prevent change to cpuset
* structures. Note that cpuset_mutex needs to be a mutex as it is used in
* paths that rely on priority inheritance (e.g. scheduler - on RT) for
* correctness.
--
2.47.0
Powered by blists - more mailing lists