On Wed, Feb 08, 2017 at 12:37:18PM -0800, Andrey Vagin wrote:
> On Wed, Feb 08, 2017 at 12:05:37AM +0300, Cyrill Gorcunov wrote:
> > The main idea is to be able to operate with container
> > at the moment where its processess and resources are
> > already restored but the processes are not yet in
On Wed, Feb 08, 2017 at 12:05:37AM +0300, Cyrill Gorcunov wrote:
> The main idea is to be able to operate with container
> at the moment where its processess and resources are
> already restored but the processes are not yet in
> running state, ie just before we kick them.
>
> Beside the need of
On Wed, Feb 08, 2017 at 07:47:30PM +0300, Andrey Ryabinin wrote:
> cgroup_add_ve_root_files() takes ->i_mutex with cgroup_mutex
> held which is unsafe because it violates lock order in the rest
> of cgroup code:
>
> ==
> [ INFO: possible
cgroup_add_ve_root_files() takes ->i_mutex with cgroup_mutex
held which is unsafe because it violates lock order in the rest
of cgroup code:
==
[ INFO: possible circular locking dependency detected ]
3.10.0-514.6.1.vz7.28.3.debug #1 Not
It contained functions missing in 2.6.18-x kernels.
https://jira.sw.ru/browse/PSBM-51358
Signed-off-by: Konstantin Khorenko
---
drivers/block/ploop/Makefile | 2 +-
drivers/block/ploop/compat.c | 118 ---
2 files changed, 1
task_ve_name() requires rcu_read_lock() held
===
[ INFO: suspicious RCU usage. ]
3.10.0-514.6.1.vz7.28.5.debug #1 Not tainted
---
kernel/ve/ve.c:165 suspicious rcu_dereference_check() usage!
Call Trace:
[] dump_stack+0x1e/0x20
[]