Cc: Tilman Schmidt <tilman@...>, Andrew Morton <akpm@...>, <linux-kernel@...>, Thomas Renninger <trenn@...>, Len Brown <len.brown@...>, Linus Torvalds <torvalds@...>, Christoph Hellwig <hch@...>, Markus Gaugusch <dsdt@...>, <linux-acpi@...>
On Fri, 2008-03-14 at 21:51 +0100, Eric Piel wrote:
I *can* probably do it earlier, maybe even statically, but I think
you're missing the point a bit here. We've just been super lucky so far
that populate_rootfs() doesn't depend on any other initcalls (or at
least BUG_ON() because of them). There may be some more buglets hiding
around.
It'd be a shame to have to have "super_early_fs_initcall()" logic for
every part of the VFS or any other initcall for that matter that you
might need. How do we tell all future VFS hackers that they have to do
this so that the next guy doesn't break it? I certainly missed it. :)
We could separate out the initcalls and just have the fs ones run before
the rest do. But, I'm not sure what interactions *THAT* might have.
There are arch-specific initcalls, and I have no idea if the fs init
code depends on *those*. That's a lot of code to check.
It is nailed when you the patch says:
+ /*
+ * Never do this at home, only the user-space is allowed to open a file.
+ * The clean way would be to use the firmware loader. But this code must be run
+ * before there is any userspace available. So we need a static/init firmware
+ * infrastructure, which doesn't exist yet...
+ */
I think requiring FS access this early in the boot processes is just
broken. It seems like the author of the patch knew a better way and
tried to get away with a hack. I think it backfired. :)
-- Dave
--
