[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090218145037.GA24240@redhat.com>
Date: Wed, 18 Feb 2009 15:50:37 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Jiri Slaby <jirislaby@...il.com>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
tglx@...utronix.de, x86@...nel.org
Subject: Re: mmotm 2009-02-17-12-33 uploaded
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.
--
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