On 2015-08-28 02:58PM +0200, David Henningsson wrote: > > On 2015-08-28 14:48, Ahmed S. Darwish wrote: > > > > The PA daemon currently uses a system-wide SHM file for all clients > > sending and receiving commands using the srbchannel low-latency > > mechanism. > > > > To be able to safely run PA daemon in system mode later using memfds, > > and to provide the necessary ground work for policy and sandboxing, > > create the srbchannel SHM files on a per-client basis. > > > > Signed-off-by: Ahmed S. Darwish <darwish.07 at gmail.com> > > Looks good as a start, but notice that this will not fix security, as the > audio is still routed over the ordinary mempool. > Thanks :-) Regarding the mempools, after doing doing some inspection, there are only two remaining: - One is created by the client using pa_context_new(), and seems to be the main one for sending audio from client to daemon. Do we have to do anything about it? - The other is created, system-wide, by the daeamon at pa_core->mempool. I still did not check what this one is used for. Any advice? > > Would be interesting to know how this affects memory usage though. > I agree. Let's measure memory consumption vs. an increasing number of connected PA clients and see the resulting graph before and after. Regards, -- Darwish http://darwish.chasingpointers.com
