Can you explain your thinking? From my understanding of the issue as an extreme example you could have a "write a backdoored .bashrc, then wait 5 minutes" repeated a thousand times queued as async i/o. If malware did this you couldn't just kill the process to stop it. You would have to shutdown the machine.
Being able to stop this loop by just killing the process is a cleaner abstraction from my perspective.
Typically there is also a latency trade off, so you can choose security and performance while losing latency. Systems should not depend on processes being fast to terminate anyways so making it slower in this case is fine.
Comments
Can you explain your thinking? From my understanding of the issue as an extreme example you could have a "write a backdoored .bashrc, then wait 5 minutes" repeated a thousand times queued as async i/o. If malware did this you couldn't just kill the process to stop it. You would have to shutdown the machine.
Being able to stop this loop by just killing the process is a cleaner abstraction from my perspective.
Security and performance are often have different, contradictory needs.
The meltdown+spectre saga showed this for speculative execution. This is no different.
Typically there is also a latency trade off, so you can choose security and performance while losing latency. Systems should not depend on processes being fast to terminate anyways so making it slower in this case is fine.