mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-31 22:25:38 -04:00
8e32afb863
The hooks were previously used to unlock the loop but now that the lock is handled inside the loop itself and we don't unlock before the blocking read anymore, we should also not call the hooks. The blocking invoke function is not meant to be called with any of the loop context locks acquired in order to avoid a deadlock. Make this (and other blocking risks) clear in the documentation. See #4472 |
||
|---|---|---|
| .. | ||
| cpu-arm.c | ||
| cpu-riscv.c | ||
| cpu-x86.c | ||
| cpu.c | ||
| dbus.c | ||
| evl-plugin.c | ||
| evl-system.c | ||
| journal.c | ||
| logger.c | ||
| loop.c | ||
| meson.build | ||
| node-driver.c | ||
| null-audio-sink.c | ||
| plugin.c | ||
| system.c | ||