[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m18wgbc0g3.fsf@fess.ebiederm.org>
Date: Fri, 18 Sep 2009 16:11:56 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Oleg Nesterov <oleg@...hat.com>, Wu Fei <at.wufei@...il.com>,
Ingo Molnar <mingo@...e.hu>, arjan@...radead.org,
jeremy@...p.org, mschmidt@...hat.com, mingo@...hat.com,
hpa@...or.com, linux-kernel@...r.kernel.org, tj@...nel.org,
tglx@...utronix.de, Andrew Morton <akpm@...ux-foundation.org>,
linux-tip-commits@...r.kernel.org,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 0/1] kthreads: simplify !kthreadd_task logic, kill kthreadd_task_init_done
Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Fri, 18 Sep 2009, Oleg Nesterov wrote:
>>
>> Not sure I understand... We don't have CLONE_PID, and kthreadd()
>> shouldn't have pid == 0 anyway.
>
> Ahh, we got rid of CLONE_PID a long time ago, and renamed it to
> CLONE_IDLETASK (which was what it was used for).
>
> As to why pid == 0 wouldn't work, I don't know, but I'll take your word
> for it.
It probably would work but it would not be visible in proc Making a kernel
thread that actually does work seems undesirable.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists