[Devel] [PATCH vz7] fuse: fuse_prepare_write() should not wait on fuse-writeback

2016-12-02 Thread Maxim Patlasov
The patch fixes a silly mistake: when fuse_prepare_write() calls __fuse_readpage(), the latter will do fuse_wait_on_page_writeback_or_invalidate anyway, so explicit fuse_wait_on_page_writeback is redundant. That silly mistake resulted in deadlock because, fuse_prepare_write used fuse_wait_on_page_

[Devel] [PATCH RH7] vfs: add warning in guard_bio_eod() if truncated_bytes > bvec->bv_len

2016-12-02 Thread Pavel Tikhomirov
https://jira.sw.ru/browse/PSBM-55105 In bug we crashed in zero_fill_bio when trying to zero memset bio_vec: struct bio_vec { bv_page = 0xea0004437500, bv_len = 4294948864, bv_offset = 0 } which is bigger than its bio->bi_size = 104448, guard_bio_eod might lead to these bv_len overflow

[Devel] [PATCH RHEL7 COMMIT] kvm/x86: skip async_pf when in guest mode

2016-12-02 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.36.1.vz7.20.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.36.1.vz7.20.9 --> commit 5173f45a28cdf3d5808e236eab882273a760a363 Author: Roman Kagan Date: Fri Dec 2 18:35:41 2016 +0400 kvm/x86: skip

[Devel] [PATCH RHEL7 COMMIT] fuse: no mtime flush on fdatasync

2016-12-02 Thread Konstantin Khorenko
The commit is pushed to "branch-rh7-3.10.0-327.36.1.vz7.20.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-327.36.1.vz7.20.9 --> commit 2b3926333196c731257c173f7be35d4bd8a4 Author: Maxim Patlasov Date: Fri Dec 2 18:34:57 2016 +0400 fuse: no mt

Re: [Devel] [PATCH vz7] fuse: no mtime flush on fdatasync

2016-12-02 Thread Dmitry Monakhov
Maxim Patlasov writes: > fuse_fsync_common() may skip fuse_flush_mtime() if datasync=1 because > mtime is pure metadata and the content of file doesn't depend on it. > > https://jira.sw.ru/browse/PSBM-55919 > > Signed-off-by: Maxim Patlasov ACK. > --- > fs/fuse/file.c |4 ++-- > 1 file cha

[Devel] [PATCH] kvm/x86: skip async_pf when in guest mode

2016-12-02 Thread Roman Kagan
Async pagefault machinery assumes communication with L1 guests only: all the state -- MSRs, apf area addresses, etc, -- are for L1. However, it currently doesn't check if the vCPU is running L1 or L2, and may inject To reproduce the problem, use a host with swap enabled, run a VM on it, run a nes