From f5b5c3a990f4a43c12e7a1fa3ded5e4b28b82453 Mon Sep 17 00:00:00 2001
From: Xuehan Xu <xxhdx1985126@gmail.com>
Date: Mon, 15 Aug 2022 22:00:46 +0800
Subject: [PATCH] crimson/os/seastore/cache: set extent's state to INVALID when
 invalidating it

Previously, when invalidating a non-conflict extent, I forgot to set its state

Signed-off-by: Xuehan Xu <xxhdx1985126@gmail.com>
---
 src/crimson/os/seastore/cache.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/crimson/os/seastore/cache.cc b/src/crimson/os/seastore/cache.cc
index c119260e45e..4b5196b646e 100644
--- a/src/crimson/os/seastore/cache.cc
+++ b/src/crimson/os/seastore/cache.cc
@@ -804,6 +804,7 @@ void Cache::invalidate_extent(
 {
   if (!extent.may_conflict()) {
     assert(extent.transactions.empty());
+    extent.state = CachedExtent::extent_state_t::INVALID;
     return;
   }