summaryrefslogtreecommitdiff
path: root/man/sd_event_add_signal.xml
diff options
context:
space:
mode:
authorLuca Boccassi <bluca@debian.org>2023-04-25 01:46:22 +0100
committerLuca Boccassi <bluca@debian.org>2023-04-25 12:24:25 +0100
commit2eeff0f4f1af40eb0c22d869c50eb364e2a5d489 (patch)
treef597ff1036eedf1023ff3a1ed538a5e7c5e2f5ae /man/sd_event_add_signal.xml
parente046719b749ebba5d44d92c7e0a9fb207d545ff7 (diff)
downloadsystemd-2eeff0f4f1af40eb0c22d869c50eb364e2a5d489.tar.gz
sd-event: store and compare per-module static origin id
sd-event objects use hashmaps, which use module-global state, so it is not safe to pass a sd-event object created by a module instance to another module instance (e.g.: when two libraries static linking sd-event are pulled in a single process). Initialize a random per-module origin id and store it in the object, and compare it when entering a public API, and error out if they don't match, together with the PID.
Diffstat (limited to 'man/sd_event_add_signal.xml')
-rw-r--r--man/sd_event_add_signal.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/sd_event_add_signal.xml b/man/sd_event_add_signal.xml
index 3e8536e961..29a7823974 100644
--- a/man/sd_event_add_signal.xml
+++ b/man/sd_event_add_signal.xml
@@ -165,7 +165,7 @@
<varlistentry>
<term><constant>-ECHILD</constant></term>
- <listitem><para>The event loop has been created in a different process.</para></listitem>
+ <listitem><para>The event loop has been created in a different process, library or module instance.</para></listitem>
</varlistentry>
<varlistentry>