Timeline for How to cause kernel panic with a single command?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2021 at 17:40 | comment | added | TopherIsSwell | The kernel is not meant to keep running no matter what. The kernel is meant to be stable for as long as possible. If a condition is detected where the kernel cannot ensure a consistent environment, it should panic rather than attempt to process data in an unknown state. A node crashing is a lot easier to deal with then your application suddenly giving away free cars to every visitor because the hardware lost its mind and the kernel just ignored it. | |
| Aug 10, 2020 at 20:06 | history | edited | Zombo | CC BY-SA 4.0 | edited body |
| Apr 30, 2020 at 14:42 | comment | added | theist | op (like me) might be interested in how to fire a kernel panic to debug how its infrastructure reacts when a node gets down. I for example came here looking for a way to do chaos testing in my AWS infra. | |
| Feb 27, 2013 at 1:43 | comment | added | Vreality | @DesmondHume A good setup doesn't crash due to too many processes. Look in to the /etc/security/limits.conf file. | |
| Feb 26, 2013 at 23:27 | comment | added | Desmond Hume | Well, there is no much use of the kernel when the system has been completely frozen by a non-sudoing user who issued a command in the likeness of :(){ :|:& };:. | |
| Feb 26, 2013 at 19:40 | history | answered | vonbrand | CC BY-SA 3.0 |