public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH][BUGFIX] cgroups: fix pid namespace bug
Date: Thu, 02 Jul 2009 09:45:04 +0800	[thread overview]
Message-ID: <4A4C1120.2090905@cn.fujitsu.com> (raw)
In-Reply-To: <6599ad830907011836x5eccc83eyc896a67295a6486d@mail.gmail.com>

Paul Menage wrote:
> Thanks Li - but as I said to Serge in the email when I brought this up
> originally, I already had a patch in mind for this; I've had an intern
> (Ben) at Google working on it. His patch (pretty much ready, and being
> sent out tomorrow I hope) is pretty similar to yours, but his is on
> top of another patch that provides a (currently read-only)
> "cgroup.procs" file in each cgroup dir that lists the unique tgids in
> the cgroup. So the key in the list of pid arrays is actually a pid_ns
> and a file type (indicating procs or tasks) rather than just a pid_ns.
> 
> So I think it makes more sense to not use this patch, but to use the
> pair of patches that Ben's written, since they provide more overal
> functionality.
> 

It's fine for me. I waited for your fix for a week or so but didn't see
it, so I thought you were stuck in other business and I did this fix.


  reply	other threads:[~2009-07-02  1:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  1:24 [PATCH][BUGFIX] cgroups: fix pid namespace bug Li Zefan
2009-07-02  1:36 ` Paul Menage
2009-07-02  1:45   ` Li Zefan [this message]
2009-07-02  1:57   ` KAMEZAWA Hiroyuki
2009-07-02 11:40     ` Balbir Singh
2009-07-02  2:17   ` Li Zefan
2009-07-02  2:20     ` Paul Menage
2009-07-02  2:28       ` Li Zefan
2009-07-02 13:26         ` Serge E. Hallyn
2009-07-02 15:43           ` Paul Menage
2009-07-02 16:15             ` Serge E. Hallyn
2009-07-02 16:27               ` Paul Menage
2009-07-02 23:20                 ` Andrew Morton
2009-07-02 23:29                   ` Paul Menage
2009-07-04  9:13             ` Eric W. Biederman
2009-07-02 13:58 ` Serge E. Hallyn
2009-07-02 16:26 ` Paul Menage
2009-07-02 16:37   ` Serge E. Hallyn
2009-07-02 16:46     ` Paul Menage
2009-07-02 19:14       ` Serge E. Hallyn

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=4A4C1120.2090905@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=serue@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox