News for hackers. Stuff that matters.
Re:Google assigns a CVE for libwebp and gives it a 10.0 score by hot_gril on Tuesday September 26, 2023 @08:05PM (#37667720)
The only overhead I see in theory is the additional process's kernel resources, which are negligible. Wherever you'd normally write to memory for some unsafe code to mutate, you instead write to the shared memory. Kernel is doing the same virtual mem protection either way, only in this case it opens up access to the child process too.

Am I missing something else, like shared mem being slower? Maybe the inability to share CPU caches?

Re:Google assigns a CVE for libwebp and gives it a 10.0 score by vacuity on Tuesday September 26, 2023 @08:17PM (#37667868)
The fact that you have a whole other process, was my line of thinking. If the scheduling doesn't play nice then latency will suffer. I don't really know in practice though.
Re:Google assigns a CVE for libwebp and gives it a 10.0 score by hot_gril on Tuesday September 26, 2023 @08:31PM (#37667999)
Latency is an issue with file or network-based IPC, but shared memory is supposed to be the same speed as non-shared. The kernel is already preventing your process from accessing others' virt mem, so presumably all it has to do for the shared mem is... not do that (for those particular processes and mem region).