From cfaf0d279fc5c60f4a1d38f342479917e923f8f6 Mon Sep 17 00:00:00 2001 From: Adam Rutkowski Date: Wed, 10 Apr 2019 14:36:07 -0400 Subject: [PATCH] Abort cache deinit in case of ocf stop fatal error We should only proceed with deinitialization in case of cache write error, not just any error. Signed-off-by: Adam Rutkowski --- modules/cas_cache/layer_cache_management.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/cas_cache/layer_cache_management.c b/modules/cas_cache/layer_cache_management.c index 5d7ff5d..12e57ac 100644 --- a/modules/cas_cache/layer_cache_management.c +++ b/modules/cas_cache/layer_cache_management.c @@ -1555,6 +1555,8 @@ int cache_mng_exit_instance(ocf_cache_id_t id, int flush) /* Stop cache device */ status = _cache_mng_cache_stop_sync(cache); + if (status && status != -OCF_ERR_WRITE_CACHE) + goto unlock; if (!status && flush_status) status = -KCAS_ERR_STOPPED_DIRTY;