Bug#783990: efivarfs is a separate fs and needs moutning

Ian Jackson ijackson at chiark.greenend.org.uk
Fri Jul 16 18:36:33 BST 2021

The Wanderer writes ("Re: Bug#783990: efivarfs is a separate fs and needs moutning"):
> Wouldn't testing the existence of
> /lib/modules/`uname -r`/kernel/fs/efivarfs/efivarfs.ko
> be enough, and probably more reliable?

I'm doubt very much it would be more reliable.  What if the kernel
reorganises its modules ?

Also, it would then have to be OR-ed with the check in
/proc/filesystems, since you might have the module built-in.

> (I'm assuming that the test which skips because "fstype not available"
> comes before the one which skips because "already mounted", and that's
> why I saw the warning even though it seems to be up and working on my
> machine.)

Yes, the tests are indeed in that order.  I think you have it mounted
now because of the apparmor fixup you found.  The change to
mountkernfs was ineffective on your system for the same reason it was
ineffective on mine, but the apparmor workaround means you don't see
the effects since apparmor has got it mounted by the time you log in.

> I need to do some other things for a while, so I won't be rebooting
> again immediately, but I'll probably test this sometime this afternoon.
> My current biggest concern about this is:
> -- 

No objections then ? :-)  (I think you may have missed a bit...)


Ian Jackson <ijackson at chiark.greenend.org.uk>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

More information about the Debian-init-diversity mailing list