On Thu, 2013-02-28 at 12:38 +0100, Tom Gundersen wrote: > Hi James, > > On Thu, Feb 28, 2013 at 11:26 AM, James Bottomley > <jbottomley@xxxxxxxxxxxxx> wrote: > > Currently you can't mount efivarfs unless the efivar module is already > > inserted. This is contrary to the usual way in linux, where we autoload > > the necessary filesystem modules when a mount request is received. The > > reason this doesn't happen for efivarfs is because the module is called > > efivars not efivarfs. Fix this by adding a module alias for efivarfs. > > I posted a similar patch recently [0], but it does not really solve > the problem as /sys/firmware/efi/efivars (which is the standard > mountpoint for this fs) does not exist unless the efivars module is > loaded. I believe a proper solution is in the works [1], which will > split out all the various parts nicely into separate modules. That depends whether you mount there or not. If you want a filesystem in /sys, then you have the same problem as debugfs and cgroupfs, so it can't be done without distro support: specifically a fstab entry, so this patch is as far as the kernel should go. Even a split won't solve the problem that the directory won't exist until the modules are loaded and the modules are autoloaded by the mount call, so the problem is the same whether the modules are split or monolithic. We definitely need this patch in 3.8 because that's where the efivarfs filesystem was added, so it should probably have a cc stable which I forgot. James -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
