| |||||||||||||
Fast interprocess communication revisitedFast interprocess communication revisitedPosted Nov 17, 2011 14:24 UTC (Thu) by renox (subscriber, #23785)In reply to: Fast interprocess communication revisited by neilbrown Parent article: Fast interprocess communication revisited
> I wonder about the wisdom of using a shared-memory locks (such as a futex) between process with different uids
I don't think that Binder is for 'untrusted' usage, if I read correctly the article if you send a message it becomes immediately part of the memory of the destination process, so it seems to be easy to create a DOS (increase the memory usage of the destination process too much and it would be killed) but maybe there are safeguards which weren't mentioned..
(Log in to post comments)
Fast interprocess communication revisited Posted Nov 17, 2011 19:53 UTC (Thu) by neilbrown (subscriber, #359) [Link]
When a processes calls mmap on the binder fd, it specifies how much space to map. Binder refused to map more than 4Meg. If you send a message to a process and it doesn't have room in that space to store the message, you get an error back.
So the worst one process can do to another is fill up its incoming queue so that it cannot get real work done.
|
|||||||||||||