pipewire/src
Wim Taymans 5ccaf29793 stream: only mmap buffers when not already mapped
Don't just blindly mmap the buffer but only when the data pointer
is NULL. If it was mapped already by the peer or the adapter or the
buffer allocation, we don't want to mmap it again and override the buffer
data pointer.

Also mmap with the permissions on the data. There is not much point in
limiting the permissions for an input port (to read only). We could do
this but then we would not be allowed to modify the existing data
pointer. The problem is that when the stream mmaps the data as READ only
and set the data pointer, if it is then handed to the mixer, it would
assume it is mapped with the permissions and then segfault when it
tries to write to the memory. It's just better to only mmap when the
data is NULL.
2025-10-06 13:17:00 +02:00
..
daemon systemd: remove RestrictNamespaces from service file 2025-09-17 10:21:10 +02:00
examples examples: avoid mmap in the example 2025-10-06 11:17:08 +02:00
gst pipewiresrc: Fix caps leak 2025-09-15 18:01:53 +00:00
modules filter-graph: allow 8 channels in max plugin 2025-09-29 14:11:27 +00:00
pipewire stream: only mmap buffers when not already mapped 2025-10-06 13:17:00 +02:00
tests tests: endpoint: fix valgrind uninit warning 2025-07-20 18:36:20 +02:00
tools tools: fix compilation after removal of field 2025-10-02 16:39:18 +02:00
meson.build meson.build: fix compile with -Dexamples=disabled 2023-11-28 10:18:25 +00:00