From: Martin Wilck <mwilck@xxxxxxxx> While we access running_state only under the config_lock, we sometimes do in a loop. Use the volatile qualifier to make sure compilers can't optimize away the loads. Reviewed-by: Benjamin Marzinski <bmarzins@xxxxxxxxxx> Signed-off-by: Martin Wilck <mwilck@xxxxxxxx> --- multipathd/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/multipathd/main.c b/multipathd/main.c index e3f2328..d081b3e 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -126,7 +126,7 @@ int poll_dmevents = 0; int poll_dmevents = 1; #endif /* Don't access this variable without holding config_lock */ -enum daemon_status running_state = DAEMON_INIT; +volatile enum daemon_status running_state = DAEMON_INIT; pid_t daemon_pid; pthread_mutex_t config_lock = PTHREAD_MUTEX_INITIALIZER; pthread_cond_t config_cond; -- 2.28.0 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
