Files
finit/src
Joachim Wiberg 9875e76419 dbus: let a dropped peer outlive its own read loop
A peer can be dropped from inside its own read loop: a handler emits a
signal, the write to that very peer fails, and the drop lands while
link_connection_process() still holds the connection and will touch
its rx buffer on the way out.  Freeing there pulls the ground out from
under it.  Unlink the peer and let the event loop free it once the
stack has unwound.

The work has to be scheduled with a non-zero delay.  A uev timer armed
with zero is a disarmed timer, so the queue would never run and the
connections would leak instead.

Losing a peer is also not a warning.  It is what shutdown looks like
from here, and every reboot said so on the console.

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
2026-08-13 10:15:06 +02:00
..
2025-07-06 03:28:42 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2026-08-05 17:59:11 +02:00
2025-07-10 14:34:16 +02:00
2026-08-13 09:28:26 +02:00
2025-07-10 14:34:16 +02:00
2026-04-26 22:11:19 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2026-08-13 09:28:26 +02:00
2026-08-13 09:28:26 +02:00
2026-05-11 21:09:02 +02:00
2025-07-10 14:34:16 +02:00
2026-02-27 10:34:38 +01:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00
2025-07-10 14:34:16 +02:00