From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: "Jan Lübbe" <j.luebbe@pengutronix.de>,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>
Subject: [PATCH v2 2/4] fs: qemu_fw_cfg: handle non-existent opt/org.barebox.env key gracefully
Date: Tue, 25 Nov 2025 07:23:47 +0100 [thread overview]
Message-ID: <20251125062603.2614867-5-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20251125062603.2614867-2-a.fatoum@pengutronix.de>
QEMU fw_cfg file system driver is the sole user of
defaultenv_append_runtime_directory() and it passes a path that's not
necessarily available.
When that happens, this is not noticed until the loop in defaultenv_load()
aborts early with an -ENOENT preventing load of an external environment.
Fix this as by not adding the directory if it doesn't exist.
Fixes: 31dfb561d1a4 ("fs: qemu_fw_cfg: support populating environment via QEMU fw_cfg")
Reported-by: Jan Lübbe <j.luebbe@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
v1 -> v2:
- move stat outside of probe, otherwise we end up with the mount
twice, because the automount triggers before the probe is complete
and the DCACHE_MOUNTED flag is set.
---
fs/qemu_fw_cfg.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/fs/qemu_fw_cfg.c b/fs/qemu_fw_cfg.c
index 5aaf14267f88..d0414b127c59 100644
--- a/fs/qemu_fw_cfg.c
+++ b/fs/qemu_fw_cfg.c
@@ -20,6 +20,8 @@
#include <linux/err.h>
#include <linux/ctype.h>
+#define FW_CFG_BAREBOX_ENV "/mnt/fw_cfg/by_name/opt/org.barebox.env"
+
struct fw_cfg_fs_inode {
struct inode inode;
const char *name;
@@ -376,8 +378,6 @@ static int fw_cfg_fs_probe(struct device *dev)
if (ret)
goto free_data;
- defaultenv_append_runtime_directory("/mnt/fw_cfg/by_name/opt/org.barebox.env");
-
return 0;
free_data:
free(data);
@@ -410,10 +410,12 @@ coredevice_initcall(qemu_fw_cfg_fs_init);
static int qemu_fw_cfg_early_mount(void)
{
+ struct stat s;
int fd;
/*
- * Also triggers the automount, so ramfb device can be detected
+ * Also triggers the automount, so both ramfb device can be detected
+ * and environment can be loaded
*/
fd = open("/mnt/fw_cfg/by_name/etc/ramfb", O_WRONLY);
if (fd >= 0) {
@@ -423,6 +425,9 @@ static int qemu_fw_cfg_early_mount(void)
platform_device_register(dev);
}
+ if (!stat(FW_CFG_BAREBOX_ENV, &s) && S_ISDIR(s.st_mode))
+ defaultenv_append_runtime_directory(FW_CFG_BAREBOX_ENV);
+
return 0;
}
late_initcall(qemu_fw_cfg_early_mount);
--
2.47.3
next prev parent reply other threads:[~2025-11-25 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 6:23 [PATCH v2 1/4] fs: qemu_fw_cfg: make use of the automount Ahmad Fatoum
2025-11-25 6:23 ` Ahmad Fatoum [this message]
2025-11-25 6:23 ` [PATCH v2 3/4] defaultenv: don't abort defaultenv_load silently on error Ahmad Fatoum
2025-11-25 6:23 ` [PATCH v2 4/4] defaultenv: add base and external defaultenv in pure_initcall Ahmad Fatoum
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=20251125062603.2614867-5-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=j.luebbe@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox