From f215835cb88fd18fca68561b8ff1149632939e94 Mon Sep 17 00:00:00 2001 From: Daan De Meyer Date: Wed, 26 Feb 2025 22:34:33 +0100 Subject: [PATCH] exec-invoke: Fix invalid use of error variable Follow up for 406f1775017a5631bc91a1f53ac5e50f4fbfac0c --- src/core/exec-invoke.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/core/exec-invoke.c b/src/core/exec-invoke.c index 6929dc1c154..10f425139bf 100644 --- a/src/core/exec-invoke.c +++ b/src/core/exec-invoke.c @@ -5193,7 +5193,7 @@ int exec_invoke( if (needs_sandboxing && exec_needs_pid_namespace(context)) { if (params->pidref_transport_fd < 0) { *exit_status = EXIT_NAMESPACE; - return log_exec_error_errno(context, params, r, "PidRef socket is not set up: %m"); + return log_exec_error_errno(context, params, SYNTHETIC_ERRNO(ENOTCONN), "PidRef socket is not set up: %m"); } /* If we had CAP_SYS_ADMIN prior to joining the user namespace, then we are privileged and don't need -- 2.47.3