[dm-devel] [PATCH 5/5] multipathd: remove volatile qualifier from running_state
mwilck at suse.com
mwilck at suse.com
Mon Mar 14 21:30:36 UTC 2022
From: Martin Wilck <mwilck at suse.com>
running_state is only accessed while holding the config_lock, the
volatile qualifier is superfluous.
Suggested-by: Benjamin Marzinski <bmarzins at redhat.com>
Signed-off-by: Martin Wilck <mwilck at suse.com>
---
multipathd/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/multipathd/main.c b/multipathd/main.c
index 2424db7..b47a457 100644
--- a/multipathd/main.c
+++ b/multipathd/main.c
@@ -127,7 +127,7 @@ static int poll_dmevents = 0;
static int poll_dmevents = 1;
#endif
/* Don't access this variable without holding config_lock */
-static volatile enum daemon_status running_state = DAEMON_INIT;
+static enum daemon_status running_state = DAEMON_INIT;
/* Don't access this variable without holding config_lock */
static bool __delayed_reconfig;
pid_t daemon_pid;
--
2.35.1
More information about the dm-devel
mailing list