3 ms·
More recently there was "rm -rf /" wiping efivars and bricking some motherboards with shitty uefi implementations thanks to systemd mounting efivars rw by defau
by gpm 3y ago
More recently there was "rm -rf /" wiping efivars and bricking some motherboards with shitty uefi implementations thanks to systemd mounting efivars rw by default (and shitty motherboard firmware). The kernel "fixed" this by mounting unknown efivars as (mostly) immutable.
https://www.phoronix.com/news/UEFI-rm-root-directory https://www.phoronix.com/news/UEFI-rm-root-directory
https://www.kernel.org/doc/html/latest/filesystems/efivarfs.html https://www.kernel.org/doc/html/latest/filesystems/efivarfs....
- cesarb 3y agoThere were also some motherboards with shitty UEFI implementations which got bricked when the efivars storage did not have enough free space to do the garbage collection. The kernel "fixed" this by not allowing more than half of the efivars storage to be used (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=68d929862e29a8b52a7f2f2f86a0600423b093cd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...).
- bscphil 3y agoRight, this is what I meant by the EFI brick in my comment. And in my comment "I can't say I've heard of that happening", I meant bricking a device on a system update. That's the specific thing which seems to happen on occasion with macOS, but that I've not seen with Linux. I do grant that there have been some (very rare) instances like this where hardware can be bricked by a command run on a Linux system.