From: "mingzhu.wang(王明珠)" <mingzhu.wang@transsion.com>
To: "kees@kernel.org" <kees@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"david@redhat.com" <david@redhat.com>
Cc: "dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"rppt@kernel.org" <rppt@kernel.org>,
"surenb@google.com" <surenb@google.com>,
"mhocko@suse.com" <mhocko@suse.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Jiazi Li" <jqqlijiazi@gmail.com>,
"peixuan.qiu(仇培旋)" <peixuan.qiu@transsion.com>
Subject: [PATCH v2] kernel/fork: Update obsolete use_mm references to kthread_use_mm
Date: Wed, 7 Jan 2026 08:15:32 +0000 [thread overview]
Message-ID: <KUZPR04MB8965F954108B4DD7E8FFDB2B8F84A@KUZPR04MB8965.apcprd04.prod.outlook.com> (raw)
The comment for get_task_mm() in kernel/fork.c incorrectly
references the deprecated function `use_mm()`, which has been renamed
to `kthread_use_mm()` in kernel/kthread.c.
This patch updates the documentation to reflect the current function
names, ensuring accuracy when developers refer to the kernel thread
memory context API.
No functional changes were introduced.
Signed-off-by: mingzhu.wang <mingzhu.wang@transsion.com>
---
v2:
- Unwrap the comment line in kernel/fork.c as requested by Michal Hocko.
- Wrap commit message lines to 75 characters as suggested by David Hildenbrand.
kernel/fork.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index b1f3915d5f8e..0c5f985cf369 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -1356,7 +1356,7 @@ struct file *get_task_exe_file(struct task_struct *task)
* @task: The task.
*
* Returns %NULL if the task has no mm. Checks PF_KTHREAD (meaning
- * this kernel workthread has transiently adopted a user mm with use_mm,
+ * this kernel workthread has transiently adopted a user mm with kthread_use_mm,
* to do its AIO) is not set and if so returns a reference to it, after
* bumping up the use count. User must release the mm via mmput()
* after use. Typically used by /proc and ptrace.
--
2.34.1
reply other threads:[~2026-01-07 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=KUZPR04MB8965F954108B4DD7E8FFDB2B8F84A@KUZPR04MB8965.apcprd04.prod.outlook.com \
--to=mingzhu.wang@transsion.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=jqqlijiazi@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peixuan.qiu@transsion.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox