←back to thread

Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” bricking UEFI

(git.kernel.org)
279 points the_why_of_y | 5 comments | 22 Feb 16 18:08 UTC | HN request time: 1.014s | source
1. gpm ◴[22 Feb 16 19:58 UTC] No.11153772[source]▶
So if I understand this correctly, now instead of bricking the system it will just fuck up the bootloader, even if the bootloader is completely unrelated to the linux install you are `rm -rf /sys`ing. Since the useful efivars that set up bootloaders must be on the whitelist.

It's an improvement, but it seems like we should do this in addition to default mounting read only.

replies(1): >>11153830 #
2. protomyth ◴[22 Feb 16 20:04 UTC] No.11153830[source]▶
It still seems to me that Linux should follow FreeBSD and not mount it as a filesystem and just use a library to manipulate the values. It clearly has some huge problems with being a filesystem. This isn't Plan 9 and everything does not have to be a file.
replies(2): >>11154628 #>>11154662 #
3. eternal_july ◴[22 Feb 16 22:01 UTC] No.11154628[source]▶
Of course everything doesn't have to be a file (it is only that way on Unices). On Linux everything is a filesystem!
4. floatboth ◴[22 Feb 16 22:06 UTC] No.11154662[source]▶
FreeBSD actually doesn't have any support for EFI variables at all! It just installs the loader into the default location (bootx64.efi) and the loader does everything.
replies(1): >>11154748 #
5. protomyth ◴[22 Feb 16 22:18 UTC] No.11154748{3}[source]▶
I guess I counted the loader as part of the system. Its installed by FreeBSD to do the job.