[Devel] [PATCH RHEL7 COMMIT] ms/new helper: wait_event_killable_exclusive()

2016-10-14 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.36.1.vz7.19.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.36.1.vz7.19.1 --> commit 33cba27d15135e157617e8ae9147baf9925f5e99 Author: Stanislav Kinsburskiy Date: Sat Oct 15

[Devel] [PATCH RHEL7 COMMIT] ms/fuse: handle only fatal signals while waiting request answer

2016-10-14 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.36.1.vz7.19.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.36.1.vz7.19.1 --> commit 1a3de6325f248eae8dfd527617fd33a5aaeea449 Author: Stanislav Kinsburskiy Date: Sat Oct 15

Re: [Devel] [PATCH 0/2] fuse: fix signals handling while processing request

2016-10-14 Thread Stanislav Kinsburskiy
14.10.2016 02:23, Maxim Patlasov пишет: Stas, The series look fine, so: Acked-by: Maxim Patlasov But, please, refine the description of the second patch. It must explain clearly why the patch fixes the problem: block_sigs() blocks ordinary non-fatal signals as

[Devel] [PATCH rh7 1/4] ms/kernel: add kcov code coverage

2016-10-14 Thread Andrey Ryabinin
From: Dmitry Vyukov kcov provides code coverage collection for coverage-guided fuzzing (randomized testing). Coverage-guided fuzzing is a testing technique that uses coverage feedback to determine new interesting inputs to a system. A notable user-space example is AFL

[Devel] [PATCH rh7 4/4] ms/kcov: properly check if we are in an interrupt

2016-10-14 Thread Andrey Ryabinin
From: Andrey Konovalov in_interrupt() returns a nonzero value when we are either in an interrupt or have bh disabled via local_bh_disable(). Since we are interested in only ignoring coverage from actual interrupts, do a proper check instead of just calling in_interrupt().

[Devel] [PATCH rh7 2/4] ms/kcov: don't trace the code coverage code

2016-10-14 Thread Andrey Ryabinin
From: James Morse Kcov causes the compiler to add a call to __sanitizer_cov_trace_pc() in every basic block. Ftrace patches in a call to _mcount() to each function it has annotated. Letting these mechanisms annotate each other is a bad thing. Break the loop by adding

[Devel] [PATCH RHEL7 COMMIT] ext4: Discard preallocated block before swap_extents

2016-10-14 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.36.1.vz7.19.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.36.1.vz7.19.1 --> commit adb6ff95974228cb22b72ab950504d46586196ac Author: Dmitry Monakhov Date: Sat Oct 15 02:14:03

[Devel] [PATCH] ext4: fix mkdir operations with overlayfs

2016-10-14 Thread Vladimir Meshkov
ext4 supports an extended operations like rename2, but inode isn't correctly marked after mkdir. Signed-off-by: Alexey Lyashkov > --- fs/ext4/namei.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/ext4/namei.c

[Devel] [PATCH rh7 3/4] ms/kcov: don't profile branches in kcov

2016-10-14 Thread Andrey Ryabinin
Profiling 'if' statements in __sanitizer_cov_trace_pc() leads to unbound recursion and crash: __sanitizer_cov_trace_pc() -> ftrace_likely_update -> __sanitizer_cov_trace_pc() ... Define DISABLE_BRANCH_PROFILING to disable this tracer.

Re: [Devel] [PATCH] ext4: fix mkdir operations with overlayfs

2016-10-14 Thread Maxim Patlasov
Thanks! You may be interested to search devel@openvz.org archives for: Subject: [PATCH rh7] ext4: ext4_mkdir must set S_IOPS_WRAPPER bit Date: Mon, 25 Jul 2016 14:01:16 -0700 On 10/14/2016 09:47 AM, Vladimir Meshkov wrote: ext4 supports an extended operations like rename2, but inode isn't