Kees Cook
Kees Cook
Can this be implemented with a Github Action instead, or is this separate?
https://lkml.org/lkml/2014/12/24/306
``` int i; for (i = 0; i < 50; i++) { if (fork() == 0) { kill(getpid(), SIGSEGV); exit(0); } } wait(NULL); ``` That should take much much longer...
Yeah, an interesting setting might be "lockout_on_oops"
The Linux kernel has just been using "#" for pre-ok diagnostics. For example: ``` 1..2 # starting foo daemon... # requesting bar # halting foo daemon ok 1 foo::bar ......
Probably the best way to deal with this kind of this is with a legit kernel driver and expose a sysfs node for the setting you're interested in. i.e. I...
And while you're at it, this one too: https://lore.kernel.org/all/[email protected]/
How is scaling normally handled with allegro? I haven't looked into this; I'd expect it to work as part of the allegro runtime (i.e. nothing I can do about it...
What is the benefit of this over having an ENOSYS default action?
Yes, this is very frustrating -- I collaborate between user ids with a shared group. This needs to respect "umask" again.