On Fri, Dec 03, 2004 at 10:44:19AM -0600, ttabi2@xxxxxxxxxxx wrote: > Arjan van de Ven wrote: > > >>What I'd like to do is create a new VMA for > >>just the memory buffer, and then lock that VMA. Locking the VMA is what > >>really locks the buffer. > > > >oh? and what stops the other thread from mucking with the VMA ? > > I don't understand your point. Multiple threads can interfere with each > other in thousands of different ways. One thread can close a file that > another opened, for example. If an app is written in such a way that it > interferes with itself, I would consider that a bug in the app. yes except that your kernel driver does these things to the app behind the apps back. And esp if the kernel side can't cope with this changing it's most likely a security hole -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
