Re: [Devel] [PATCH vz7] fuse: fuse_prepare_write() cannot handle page from killed request

2017-02-14 Thread Konstantin Khorenko
Dima, please review the patch. -- Best regards, Konstantin Khorenko, Virtuozzo Linux Kernel Team On 02/14/2017 03:03 AM, Maxim Patlasov wrote: After fuse_prepare_write() called __fuse_readpage(file, page, ...), the page might be already unlocked by fuse_kill_requests(): for (

[Devel] [PATCH] KVM: nVMX: Fix the NMI IDT-vectoring handling

2017-02-14 Thread Denis Plotnikov
From: Wanpeng Li Run kvm-unit-tests/eventinj.flat in L1: Sending NMI to self After NMI to self FAIL: NMI This test scenario is to test whether VMM can handle NMI IDT-vectoring info correctly. At the beginning, L2 writes LAPIC to send a self NMI, the EPT page tables on both L1 and L0 are empt

[Devel] [PATCH] KVM: nVMX: Fix the NMI IDT-vectoring handling

2017-02-14 Thread Denis Plotnikov
From: Wanpeng Li Run kvm-unit-tests/eventinj.flat in L1: Sending NMI to self After NMI to self FAIL: NMI This test scenario is to test whether VMM can handle NMI IDT-vectoring info correctly. At the beginning, L2 writes LAPIC to send a self NMI, the EPT page tables on both L1 and L0 are empt

Re: [Devel] [vzlin-dev] [PATCH vz7] fuse: fuse_prepare_write() cannot handle page from killed request

2017-02-14 Thread Dmitry Monakhov
Maxim Patlasov writes: > After fuse_prepare_write() called __fuse_readpage(file, page, ...), > the page might be already unlocked by fuse_kill_requests(): > >> for (i = 0; i < req->num_pages; i++) { >> struct page *page = req->pages[i]; >> Se

[Devel] [PATCH libvzctl 2/3] env_nsops: ns_set_memory_param -- Allow to select which param to set

2017-02-14 Thread Cyrill Gorcunov
In case of restore procedure we will be restoring memory limits in several steps: limiting ram first and limiting swap on later stage. Thus provide the mask to trigger the switch. Signed-off-by: Cyrill Gorcunov --- lib/env_nsops.c | 17 - 1 file changed, 12 insertions(+), 5 delet

[Devel] [PATCH libvzctl 1/3] cgroup: Allow to attach to specific cgroup only

2017-02-14 Thread Cyrill Gorcunov
Signed-off-by: Cyrill Gorcunov --- lib/cgroup.c| 4 +++- lib/cgroup.h| 2 +- lib/env_nsops.c | 4 ++-- 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/lib/cgroup.c b/lib/cgroup.c index c101a64..806cab2 100644 --- a/lib/cgroup.c +++ b/lib/cgroup.c @@ -618,11 +618,13 @@ int c

[Devel] [PATCH libvzctl 3/3] Rework setting up memory limits on restore

2017-02-14 Thread Cyrill Gorcunov
Currenlty we restore memory limits in post-resume stage where applications are already executing after restore stage which in worst scenario may cause container to stop restoration procedure. Instead lets use another strategy: - start restore with ram limited but unlimited swap - on post-restor

[Devel] [PATCH libvzctl 0/3] Rework setting up memory limits on restore

2017-02-14 Thread Cyrill Gorcunov
Igor, please ping me in PM once you're refy to merge the series: I'll rebuild new criu first with changes needed so libvzctl will require new criu to exist before the install. Cyrill Gorcunov (3): cgroup: Allow to attach to specific cgroup only env_nsops: ns_set_memory_param -- Allow to select