From 2c30250238cbd1c1976aca903cacc4abbb4f59ce Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=A9r=C3=A9mie=20Galarneau?= Date: Mon, 1 Mar 2021 15:40:48 -0500 Subject: [PATCH] Docs: document trigger condition and action ownership in 2.13+ MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Jérémie Galarneau Change-Id: I8a52f166565efc87c6073713ce0f6569ba6d3661 --- include/lttng/trigger/trigger.h | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/include/lttng/trigger/trigger.h b/include/lttng/trigger/trigger.h index de4e93d70..3b1cedda1 100644 --- a/include/lttng/trigger/trigger.h +++ b/include/lttng/trigger/trigger.h @@ -49,8 +49,11 @@ enum lttng_trigger_firing_policy { * in the emission of a notification to clients listening through * notification channels. * - * The caller retains the ownership of both the condition and action - * and both must be kept alive for the lifetime of the trigger object. + * Prior to 2.13, the caller had to retain the ownership of both the condition + * and action. Both objects had to be kept alive for the lifetime of the trigger + * object. This is no longer the case as the condition and action objects are + * internally reference counted. It is safe to destroy a condition and an action + * after using them to create a trigger. However, they should no longer be used. * * If the action is a notification action with capture descriptors, * the condition must be an event rule condition. -- 2.34.1