Exploiting races in system call wrappers
Posted Aug 16, 2007 22:04 UTC (Thu) by flewellyn
In reply to: Exploiting races in system call wrappers
Parent article: Exploiting races in system call wrappers
Sounds rather like the old "safety vs. performance" issue. Joy.
I can think of ways to make shared memory safe, in general, but most of them involve either locking critical sections, or using some kind of multiversion concurrency control, like many DBMSes do. Either one is going to cost.
In the "TOCTTOU" case, I suppose locking the "check and use" section of the code somehow, so that no other processes could access the resource being checked, would work, but again, performance hit. And complicated. And I might be wrong anyway, and that doesn't work after all.
to post comments)