The thing is that built-in modules are being inited before
rootfs mount. Some of the modules can request firmware loading
using async 'request_firmware_nowait' call just while inition,
so we can catch this kind of race: rootfs does not exist yet,
but we are going to open and load firmware file requesting from
the kernel.
This is RFC because I do not feel confident about the convention
of firmware loading. The questions are:
1. can 'request_firmware' (sync variant) be called on module inition
directly, without any threads? if can, that means firmware will
never be loaded for the driver at first try in case of built-in
module, because rootfs will be mounted only at the end of kernel
init sequence.
2. in case of separated '/lib' mount point we still have the problem:
firmware will be loaded only on further tries, but the first attempt
will always fail, because '/lib' mount point does not exist. Seems
to me this can't be simply fixed, and firmware_request logic needs
some refactoring..
Probably, there are other good questions which I do not see because
of shallow understanding of init and firmware loading sequences.
Cc: Ming Lei <ming....@canonical.com>
Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: Andrew Morton <a...@linux-foundation.org>
Cc: Paul Gortmaker <paul.gortma...@windriver.com>
Cc: Rob Landley <r...@landley.net>
Cc: Randy Dunlap <rdun...@infradead.org>
Cc: "Kirill A. Shutemov" <kirill.shute...@linux.intel.com>
Cc: Michael Opdenacker <michael.opdenac...@free-electrons.com>
Cc: Peter Zijlstra <pet...@infradead.org>
Cc: Santosh Shilimkar <santosh.shilim...@ti.com>
Cc: Hannes Frederic Sowa <han...@stressinduktion.org>
Cc: Krzysztof Mazur <krzys...@podlesie.net>
Cc: Tetsuo Handa <penguin-ker...@i-love.sakura.ne.jp>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Roman Pen <r.peni...@gmail.com>
---
drivers/base/firmware_class.c | 6 ++++++
include/linux/init.h | 4 ++++
init/main.c | 20 +++++++++++++++++++-
3 files changed, 29 insertions(+), 1 deletion(-)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index c30df50e..219ac84 100644
--- a/drivers/base/firmware_class.c
+++ b/drivers/base/firmware_class.c
@@ -28,6 +28,7 @@
#include <linux/suspend.h>
#include <linux/syscore_ops.h>
#include <linux/reboot.h>
+#include <linux/init.h>
#include <generated/utsrelease.h>
@@ -323,6 +324,11 @@ static int fw_get_filesystem_firmware(struct device
*device,
int rc = -ENOENT;
char *path = __getname();
+ /* Before any file access we have to wait for rootfs.
+ In case of built-in module we can race with kernel init
+ thread, which mounts rootfs, and driver firmware loading */
+ wait_for_rootfs();
+
for (i = 0; i < ARRAY_SIZE(fw_path); i++) {
struct file *file;
diff --git a/include/linux/init.h b/include/linux/init.h
index e168880..36e7b14 100644
--- a/include/linux/init.h
+++ b/include/linux/init.h
@@ -153,6 +153,10 @@ void prepare_namespace(void);
void __init load_default_modules(void);
int __init init_rootfs(void);
+/* Defined in init/main.c */
+void wait_for_rootfs(void);
+void wake_up_rootfs_waiters(void);
+
extern void (*late_time_init)(void);
extern bool initcall_debug;
diff --git a/init/main.c b/init/main.c
index 9c7fd4c..cc96498 100644
--- a/init/main.c
+++ b/init/main.c
@@ -931,9 +931,27 @@ static noinline void __init kernel_init_freeable(void)
/*
* Ok, we have completed the initial bootup, and
* we're essentially up and running. Get rid of the
- * initmem segments and start the user-mode stuff..
+ * initmem segments, wake up rootfs mount waiters
+ * and start the user-mode stuff..
*/
+ wake_up_rootfs_waiters();
/* rootfs is available now, try loading default modules */
load_default_modules();
}
+
+static DECLARE_COMPLETION(rootfs_mounted);
+
+void wait_for_rootfs(void)
+{
+ /* Avoid waiting for ourselves */
+ if (is_global_init(current))
+ pr_warn("kernel_init: it is not a good idea to wait for rootfs
mount from init task\n");
+ else
+ wait_for_completion(&rootfs_mounted);
+}
+
+void wake_up_rootfs_waiters(void)
+{
+ complete(&rootfs_mounted);
+}
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
