On 6/7/07, Cedric Le Goater <[EMAIL PROTECTED]> wrote:
when there's no tasks in a container, opening
//tasks
spits the following warning because we are trying to
kmalloc(0).
I guess I'm not opposed to this change - but isn't there still
discussion going on about whether kmalloc(0) should act
Hello Paul !
[EMAIL PROTECTED] wrote:
> This patch adds the per-directory "tasks" file for containerfs mounts;
> this allows the user to determine which tasks are members of a
> container by reading a container's "tasks", and to move a task into a
> container by writing its pid to its "tasks".
he
This patch adds the per-directory "tasks" file for containerfs mounts;
this allows the user to determine which tasks are members of a
container by reading a container's "tasks", and to move a task into a
container by writing its pid to its "tasks".
Signed-off-by: Paul Menage <[EMAIL PROTECTED]>
-
3 matches
Mail list logo
