From: Coly Li <colyli@suse.de>
To: mtkaczyk@kernel.org
Cc: linux-raid@vger.kernel.org, Coly Li <colyli@suse.de>
Subject: [PATCH] mdopen: add sbin path to env PATH when call system("modprobe md_mod")
Date: Tue, 21 Jan 2025 23:16:03 +0800 [thread overview]
Message-ID: <20250121151603.235606-1-colyli@suse.de> (raw)
During the boot process if mdadm is called in udev context, sbin paths
like /sbin, /usr/sbin, /usr/local/sbin normally not defined in PATH env
variable, calling system("modprobe md_mod") in create_named_array() may
fail with 'sh: modprobe: command not found' error message.
We don't want to move modprobe binary into udev private directory, so
setting the PATH env is a more proper method to avoid the above issue.
This patch sets PATH env variable with "/sbin:/usr/sbin:/usr/local/sbin"
before calling system("modprobe md_mod"). The change only takes effect
within the udev worker context, not seen by global udev environment.
Signed-off-by: Coly Li <colyli@suse.de>
---
mdopen.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/mdopen.c b/mdopen.c
index 26f0c716..30cf781b 100644
--- a/mdopen.c
+++ b/mdopen.c
@@ -39,6 +39,18 @@ int create_named_array(char *devnm)
fd = open(new_array_file, O_WRONLY);
if (fd < 0 && errno == ENOENT) {
+ char buf[PATH_MAX];
+
+ /*
+ * When called by udev worker context, path of modprobe
+ * might not be in env PATH. Set sbin paths into PATH
+ * env to avoid potential failure when run modprobe here.
+ */
+ memset(buf, 0, PATH_MAX);
+ snprintf(buf, PATH_MAX - 1, "%s:%s", getenv("PATH"),
+ "/sbin:/usr/sbin:/usr/local/sbin");
+ setenv("PATH", buf, 1);
+
if (system("modprobe md_mod") == 0)
fd = open(new_array_file, O_WRONLY);
}
--
2.47.1
next reply other threads:[~2025-01-21 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 15:16 Coly Li [this message]
2025-01-21 18:09 ` [PATCH] mdopen: add sbin path to env PATH when call system("modprobe md_mod") Mariusz Tkaczyk
2025-01-22 1:56 ` Coly Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250121151603.235606-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mtkaczyk@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.