4 ms·

It doesn't, it just loses your session

• inigyou 2mo ago
  A kernel panic doesn't bring down the CPU, nor the hard drive, or the RAM, or the power supply unit. So if we're being pedantic, the machine is still up.
  • eru 2mo ago
    Well, a kernel bug gets write access to everything. A bug in userland is a bit more constrained in what it can do. That counts especially for accidental bugs and denial of service. To make a userland bug exploited adversarially not impact the rest of the system requires more hardening of the kernel.
    • inigyou 2mo ago
      Yeah a userland bug just gets all my passwords, SSH keys, personal secrets and whatever. Say it with me - there's no practical difference.
      • eru 2mo ago
        You are talking about a single user system. You can compartmentalise further. Modern processors even give you these 'rings' to help with the hardware side of that, if you want to.
        • inigyou 2mo ago
          Yes, these are the standard excuses. But has anyone actually thought about them in the last twenty years, in the context of the way we actually use computers?
          • eru 2mo ago
            Eh, yes? Just look the discussions surrounding the development of any web browser? Or look at the permissions system in Android or iOS or on Mac (and perhaps even Windows?).
            • inigyou 2mo ago
              So you acknowledge a browser bug is just as bad as a kernel bug.
              • eru 2mo ago
                A bug in the website itself is just as bad, if it's a website you care about. They differ in how easy a fix is to develop and roll out, and what the blast radius is.
  • deleted 2mo ago
    [deleted]