With the locking reduced it opened windows for races between
running updates, pending and new updates. Current logic to
deal with them is not correct.
Current flags are:
MD_DIRTY - means md page is dirty and is waiting for writeback
MD_WRITEBACK - write back is in progress
But we drop the lock aft
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.14
-->
commit 4b8249e2da1a7d28882bd70844fc4d64db952f08
Author: Alexander Atanasov
Date: Tue Feb 11 16:25:57 2025 +0200
dm-ploop:
One in pcs_cs_accel is proven to be fatal, another one in pcs_mr
is just a finding while searching for the first one.
Signed-off-by: Alexey Kuznetsov
---
fs/fuse/kio/pcs/pcs_cs_accel.c | 2 +-
fs/fuse/kio/pcs/pcs_mr.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/
On 2/11/25 22:25, Alexander Atanasov wrote:
With the locking reduced it opened windows for races between
running updates, pending and new updates. Current logic to
deal with them is not correct.
Examples of exact race situation in code would be appreciated, as now
it's impossible to unserst
On 12.02.25 7:54, Pavel Tikhomirov wrote:
On 2/11/25 22:25, Alexander Atanasov wrote:
With the locking reduced it opened windows for races between
running updates, pending and new updates. Current logic to
deal with them is not correct.
Examples of exact race situation in code would be appre
