issue-1751: [Filestore] WriteBackCache: Replace ReadWriteRangeLock with pinning mechanism, move remaining code to TUtils

Author: Andrei Nasonov

cloud/filestore/libs/vfs_fuse/write_back_cache/node_state.h

@@ -1,13 +1,13 @@
 #pragma once
 
 #include "node_cache.h"
-#include "read_write_range_lock.h"
 
 #include <cloud/filestore/public/api/protos/data.pb.h>
 
 #include <library/cpp/threading/future/core/future.h>
 
 #include <util/generic/deque.h>
+#include <util/generic/set.h>
 
 namespace NCloud::NFileStore::NFuse::NWriteBackCache {
 
@@ -48,8 +48,8 @@ struct TNodeState
     // Tracks cached data parts
     TNodeCache Cache;
 
-    // Prevent from concurrent read and write requests with overlapping ranges
-    TReadWriteRangeLock RangeLock;
+    // Prevents flushed requests from being evicted from Cache
+    TMultiSet<ui64> CachedDataPins;
 
     ENodeFlushStatus FlushStatus = ENodeFlushStatus::NothingToFlush;
 
@@ -67,7 +67,7 @@ struct TNodeState
 
     bool CanBeDeleted() const
     {
-        if (Cache.Empty() && RangeLock.Empty()) {
+        if (Cache.Empty() && CachedDataPins.empty()) {
             Y_ABORT_UNLESS(FlushRequests.empty());
             Y_ABORT_UNLESS(FlushStatus == ENodeFlushStatus::NothingToFlush);
             return true;