From: Oleg Nesterov <oleg@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, x86@kernel.org
Subject: Re: mmotm 2009-02-17-12-33 uploaded
Date: Wed, 18 Feb 2009 15:50:37 +0100 [thread overview]
Message-ID: <20090218145037.GA24240@redhat.com> (raw)
In-Reply-To: <200902182245.27525.rusty@rustcorp.com.au>
On 02/18, Rusty Russell wrote:
>
> On Wednesday 18 February 2009 20:23:56 Andrew Morton wrote:
> > Someone else has been mucking with kthread.c in linux-next, and a
> > couple of days ago that mucking got dropped from linux-next. Perhaps
> > this churn broke Oleg's patch.
"[merged] kthread-dont-looking-for-a-task-in-create_kthread-2.patch"
has "create->result = current;" in kthread(), then this line was
lost somehow,
> Oleg and I had an accidentally-offlist chat about these patches.
>
> Last we decided, a more ambitious approach was desired. Patches RSN.
Yes, but can't we do this on top of current patches?
We are going to change the API a bit, so that kthread_create() bumps
a reference to task_struct. I think it would be nice to separate the
API changes from the implementation changes.
Oleg.
next prev parent reply other threads:[~2009-02-18 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 20:33 mmotm 2009-02-17-12-33 uploaded akpm
2009-02-17 23:21 ` Jiri Slaby
2009-02-17 23:31 ` Andrew Morton
2009-02-18 8:45 ` Jiri Slaby
2009-02-18 9:19 ` Jiri Slaby
2009-02-18 9:35 ` Jiri Slaby
2009-02-18 9:53 ` Andrew Morton
2009-02-18 12:15 ` Rusty Russell
2009-02-18 14:50 ` Oleg Nesterov [this message]
2009-04-28 19:22 ` Oleg Nesterov
2009-04-28 19:48 ` Andrew Morton
2009-04-28 20:13 ` Oleg Nesterov
2009-02-18 0:52 ` mmotm 2009-02-17-12-33 uploaded (nr_pdflush_threads_min sysctl build error) Randy Dunlap
2009-02-18 1:40 ` Andrew Morton
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=20090218145037.GA24240@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.