From: Huacai Chen <chenhuacai@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Huacai Chen <chenhuacai@loongson.cn>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] kthread: Rename user_mode_thread() to kmuser_thread()
Date: Tue, 18 Jul 2023 20:43:40 +0800 [thread overview]
Message-ID: <CAAhV-H7qk8wSFt=ZMUSUt4cAmH+-5AsGqszXNW9w+u6Y8vDN+A@mail.gmail.com> (raw)
In-Reply-To: <ZJ9kWqhRCWkLcYyv@bombadil.infradead.org>
Hi, Luis,
On Sat, Jul 1, 2023 at 7:25 AM Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> On Sun, Jun 25, 2023 at 04:55:33PM +0800, Huacai Chen wrote:
> > Friendly ping?
>
> You want to cc the folks who Nacked your patch. Until then, this
> probably can't go further.
Thank you very much. Eric and Andrew are already in the CC list, so
add Thomas now.
My brain is a little old-fashioned so I insisted that "a thread
without mm_struct should be a kernel thread" in the previous patch.
Unfortunately this makes Eric and Thomas unhappy, I'm very sorry for
that.
During the discussion of the previous patch I know I made some
mistakes about some basic concepts, but I also found the name
"user_mode_thread()" is somewhat confusing. I think rename it to
kmuser_thread() is better, because:
1, it identify init and umh as user threads;
2, it points out that init and umh are special user threads that run
in kernel mode before loading a user program.
Sorry for my rudeness again.
Huacai
>
> Luis
next prev parent reply other threads:[~2023-07-18 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:10 Huacai Chen
2023-06-25 8:55 ` Huacai Chen
2023-06-30 23:25 ` Luis Chamberlain
2023-07-18 12:43 ` Huacai Chen [this message]
2023-07-23 14:13 ` Huacai Chen
2023-09-11 12:07 ` Huacai Chen
2023-09-12 1:58 ` Eric W. Biederman
2023-09-12 15:31 ` Huacai Chen
2023-09-12 17:29 ` Eric W. Biederman
2023-09-13 12:39 ` Huacai Chen
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='CAAhV-H7qk8wSFt=ZMUSUt4cAmH+-5AsGqszXNW9w+u6Y8vDN+A@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chenhuacai@loongson.cn \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=tglx@linutronix.de \
/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