From 994cf2055d6d3cecef6a9e649f78eb3a1946be9d Mon Sep 17 00:00:00 2001 From: Radoslaw Zarzynski Date: Tue, 20 Dec 2022 15:33:51 +0000 Subject: [PATCH] osd: slightly improve readability in handling of snap trim errors I think that lowering to the indentation level for the affected `return` better shows it's eseentially "a catch all" exit. Signed-off-by: Radoslaw Zarzynski --- src/osd/PrimaryLogPG.cc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/osd/PrimaryLogPG.cc b/src/osd/PrimaryLogPG.cc index 26dbac6d526e1..29e61d8f84681 100644 --- a/src/osd/PrimaryLogPG.cc +++ b/src/osd/PrimaryLogPG.cc @@ -15698,9 +15698,8 @@ boost::statechart::result PrimaryLogPG::AwaitAsyncWork::react(const DoSnapWork&) ldout(pg->cct, 10) << "waiting for it to clear" << dendl; return transit< WaitRWLock >(); - } else { - return transit< NotTrimming >(); } + return transit< NotTrimming >(); } in_flight.insert(object); -- 2.39.5