From: Ilya Loginov <isloginov@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] fix problem with reschenduling in rest_init (2.6.35-rc3)
Date: Thu, 24 Jun 2010 17:23:34 +0400 [thread overview]
Message-ID: <20100624172334.ca7e9bef.isloginov@gmail.com> (raw)
In-Reply-To: <1277385096.1875.974.camel@laptop>
On Thu, 24 Jun 2010 15:11:36 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> However I suspect the ordering is like it is because we want init to
> have pid 1, if we were to re-order like you suggest kthreadd will end up
> with pid 1 and init with pid 2.
Strange, but init does not die after I did this. Fix me if I wrong, but it wants
to have pid 1, and die in other case.
Interesting...
--
Ilya Loginov <isloginov@gmail.com>
next prev parent reply other threads:[~2010-06-24 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 20:11 [PATCH] fix problem with reschenduling in rest_init (2.6.35-rc3) Ilya Loginov
2010-06-24 13:11 ` Peter Zijlstra
2010-06-24 13:23 ` Ilya Loginov [this message]
2010-06-24 14:08 ` Илья Логинов
2010-06-28 9:01 ` [PATCH] init: Fix race between init and kthreadd Peter Zijlstra
2010-06-28 11:53 ` [PATCH] init: Fix race between init and kthreadd -v2 Peter Zijlstra
2010-06-28 14:19 ` Ingo Molnar
2010-06-28 14:51 ` [PATCH] init: Fix race between init and kthreadd -v3 Peter Zijlstra
2010-06-28 15:03 ` Linus Torvalds
2010-06-28 16:23 ` Randy Dunlap
2010-06-28 20:24 ` [tip:sched/urgent] init, sched: Fix race between init and kthreadd tip-bot for Peter Zijlstra
2010-06-30 8:32 ` [PATCH] init: Fix race between init and kthreadd -v3 Ilya Loginov
2010-06-30 8:37 ` [PATCH] init: Fix comment Peter Zijlstra
2010-06-30 8:45 ` [tip:sched/urgent] " tip-bot for Peter Zijlstra
2010-06-28 20:06 ` [PATCH] init: Fix race between init and kthreadd -v2 Ilya Loginov
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=20100624172334.ca7e9bef.isloginov@gmail.com \
--to=isloginov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.