From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
menage@google.com, bblum@google.com, ebiederm@xmission.com,
lizf@cn.fujitsu.com, matthltc@us.ibm.com
Subject: Re: cgrooups && 2.6.32 -mm merge plans
Date: Thu, 17 Sep 2009 13:38:46 -0700 [thread overview]
Message-ID: <20090917133846.a00daece.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090917201516.GA29346@redhat.com>
On Thu, 17 Sep 2009 22:15:16 +0200
Oleg Nesterov <oleg@redhat.com> wrote:
> On 09/15, Andrew Morton wrote:
> >
> > #cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch: Oleg conniptions
> > cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch
> > cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup-fix.patch
> > cgroups-add-ability-to-move-all-threads-in-a-process-to-a-new-cgroup-atomically.patch
> >
> > Merge after checking with Oleg.
>
> Well. I think these patches are buggy :/
>
Well that's never prevented us from merging stuff before.
Thanks, I'll disable the patches for now. Do we have a grip on what's
wrong and what needs to be done to fix things?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
menage@google.com, bblum@google.com, ebiederm@xmission.com,
lizf@cn.fujitsu.com, matthltc@us.ibm.com
Subject: Re: cgrooups && 2.6.32 -mm merge plans
Date: Thu, 17 Sep 2009 13:38:46 -0700 [thread overview]
Message-ID: <20090917133846.a00daece.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090917201516.GA29346@redhat.com>
On Thu, 17 Sep 2009 22:15:16 +0200
Oleg Nesterov <oleg@redhat.com> wrote:
> On 09/15, Andrew Morton wrote:
> >
> > #cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch: Oleg conniptions
> > cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch
> > cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup-fix.patch
> > cgroups-add-ability-to-move-all-threads-in-a-process-to-a-new-cgroup-atomically.patch
> >
> > Merge after checking with Oleg.
>
> Well. I think these patches are buggy :/
>
Well that's never prevented us from merging stuff before.
Thanks, I'll disable the patches for now. Do we have a grip on what's
wrong and what needs to be done to fix things?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-09-17 20:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 23:15 2.6.32 -mm merge plans Andrew Morton
2009-09-15 23:15 ` Andrew Morton
2009-09-16 0:03 ` Paul Mundt
2009-09-16 0:03 ` Paul Mundt
2009-09-16 0:18 ` Andrew Morton
2009-09-16 0:18 ` Andrew Morton
2009-09-16 3:51 ` Mike Frysinger
2009-09-16 3:51 ` Mike Frysinger
2009-09-16 4:15 ` Andrew Morton
2009-09-16 4:15 ` Andrew Morton
2009-09-16 4:17 ` Mike Frysinger
2009-09-16 4:17 ` Mike Frysinger
2009-09-16 7:21 ` Artem Bityutskiy
2009-09-16 7:21 ` Artem Bityutskiy
2009-09-16 7:09 ` Artem Bityutskiy
2009-09-16 7:36 ` Artem Bityutskiy
2009-09-16 3:46 ` Dmitry Torokhov
2009-09-16 3:46 ` Dmitry Torokhov
2009-09-16 4:14 ` Andrew Morton
2009-09-16 4:14 ` Andrew Morton
2009-09-16 8:33 ` David Härdeman
2009-09-16 8:33 ` David Härdeman
2009-09-16 15:00 ` Bjorn Helgaas
2009-09-16 15:00 ` Bjorn Helgaas
2009-09-16 20:00 ` Andrew Morton
2009-09-16 20:00 ` Andrew Morton
2009-09-16 7:37 ` memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans) Balbir Singh
2009-09-16 7:37 ` Balbir Singh
2009-09-16 7:51 ` Daisuke Nishimura
2009-09-16 7:51 ` Daisuke Nishimura
2009-09-16 7:58 ` KAMEZAWA Hiroyuki
2009-09-16 7:58 ` KAMEZAWA Hiroyuki
2009-09-16 8:45 ` stack limits [was Re: 2.6.32 -mm merge plans] Pavel Machek
2009-09-16 8:45 ` Pavel Machek
2009-09-16 9:42 ` hwpoison fixes was Re: 2.6.32 -mm merge plans Andi Kleen
2009-09-16 9:42 ` Andi Kleen
2009-09-17 20:15 ` cgrooups && " Oleg Nesterov
2009-09-17 20:15 ` Oleg Nesterov
2009-09-17 20:38 ` Andrew Morton [this message]
2009-09-17 20:38 ` Andrew Morton
2009-09-17 21:08 ` Oleg Nesterov
2009-09-17 21:08 ` Oleg Nesterov
2009-09-17 20:32 ` do_wait() changes " Oleg Nesterov
2009-09-17 20:32 ` Oleg Nesterov
2009-09-17 20:46 ` tracehooks " Oleg Nesterov
2009-09-17 20:46 ` Oleg Nesterov
2009-09-17 21:56 ` Roland McGrath
2009-09-17 21:56 ` Roland McGrath
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=20090917133846.a00daece.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bblum@google.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=matthltc@us.ibm.com \
--cc=menage@google.com \
--cc=oleg@redhat.com \
/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.