Seen booting yesterday's linux-next, was not present in 2.6.37-rc7-mmotm1202.
Not sure if it's an selinux or cgroup issue, so I'm throwing it at every
address I can find for either. This is easily replicatable and happens at
every boot, so I can test patches if needed. Am willing to bisect it
Hi all,
in the container implementation, we are facing the problem of a process
calling the sys_reboot syscall which of course makes the host to
poweroff/reboot.
If we drop the cap_sys_reboot capability, sys_reboot fails and the
container reach a shutdown state but the init process stay
On Thu, 13 Jan 2011 12:55:04 -0600
Rob Landley rland...@parallels.com wrote:
From: Rob Landley rland...@parallels.com
Teach cifs about network namespaces, so mounting uses adresses/routing
visible from the container rather than from init context.
Signed-off-by: Rob Landley
On 01/13/2011 10:50 PM, Bruno Prémont wrote:
On Thu, 13 January 2011 Daniel Lezcanodaniel.lezc...@free.fr wrote:
On 01/13/2011 09:09 PM, Bruno Prémont wrote:
On Thu, 13 January 2011 Daniel Lezcanodaniel.lezc...@free.fr wrote:
in the container implementation, we are facing the problem of a
On 01/13/2011 09:09 PM, Bruno Prémont wrote:
On Thu, 13 January 2011 Daniel Lezcanodaniel.lezc...@free.fr wrote:
in the container implementation, we are facing the problem of a process
calling the sys_reboot syscall which of course makes the host to
poweroff/reboot.
If we drop the
Nick Piggin wrote:
On Fri, Jan 14, 2011 at 2:34 AM, valdis.kletni...@vt.edu wrote:
Seen booting yesterday's linux-next, was not present in 2.6.37-rc7-mmotm1202.
Not sure if it's an selinux or cgroup issue, so I'm throwing it at every
address I can find for either. This is easily
Just mount the cgroupfs:
# mount -t cgroup -o cpuset xxx /mnt
(oops!!)
The bug is caused by:
=
commit 0df6a63f8735a7c8a877878bc215d4312e41ef81
Author: Al Viro v...@zeniv.linux.org.uk
Date: Tue Dec 21 13:29:29 2010 -0500
switch cgroup
switching it to s_d_op allows to kill
On Fri, Jan 14, 2011 at 12:56:17PM +0800, Li Zefan wrote:
Just mount the cgroupfs:
# mount -t cgroup -o cpuset xxx /mnt
(oops!!)
The bug is caused by:
=
commit 0df6a63f8735a7c8a877878bc215d4312e41ef81
Author: Al Viro v...@zeniv.linux.org.uk
Date: Tue Dec 21 13:29:29 2010
Al Viro wrote:
On Fri, Jan 14, 2011 at 12:56:17PM +0800, Li Zefan wrote:
Just mount the cgroupfs:
# mount -t cgroup -o cpuset xxx /mnt
(oops!!)
The bug is caused by:
=
commit 0df6a63f8735a7c8a877878bc215d4312e41ef81
Author: Al Viro v...@zeniv.linux.org.uk
Date: Tue Dec 21
Oren Laadan [or...@cs.columbia.edu] wrote:
| Folks,
|
| I just pushed out a new v23-rc1 branch of linux-cr. This one is
| rebased to 2.6.37, and contains nearly all the patches pulled
| on v22-dev. I only gave it a brief test drive... feel free to
| throw all your ammo it.
Oren,
We need the
10 matches
Mail list logo