So,
to sum up the thread here:
1. Arguably, tasks which have encountered a memory error should get sent
a SIGBUS.
2. if a valid use case appears, the proper fix should be not to sprinkle
special-handling code in random syscalls in a whack-a-mole fashion
but to note somewhere in the task struct that the task has
encountered a memory error and then *override* the signal it gets
sent to it with a SIGBUS one.
I.e., this should be a generic solution, if anything.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
