X-Git-Url: https://git.lttng.org/?a=blobdiff_plain;f=include%2Flttng%2Fnotification%2Fnotification-internal.h;h=65b03672295f638250e90ce93edb5c31ef8a0e83;hb=f83bcd90ceb5ce659ffe9d7747d6f3366a09748a;hp=df9e8cb50a5549ed6525a89d2cabe74c9a747c4c;hpb=a58c490f0bff52a73717d31d04d1472629180de2;p=lttng-tools.git diff --git a/include/lttng/notification/notification-internal.h b/include/lttng/notification/notification-internal.h index df9e8cb50..65b036722 100644 --- a/include/lttng/notification/notification-internal.h +++ b/include/lttng/notification/notification-internal.h @@ -21,27 +21,14 @@ #include #include #include +#include #include #include +#include struct lttng_notification { struct lttng_condition *condition; struct lttng_evaluation *evaluation; - /* - * The ownership of the notification's inner-elements depends - * on the way it was created. The notification owns both - * the condition and evaluation if it was obtained from a notification - * channel (i.e. created using lttng_notification_create_from_buffer) - * as the user may never access the condition and evaluation, - * thus never getting a chance to free them. - * - * However, when the _private_ lttng_notification_create() function - * is used, no ownership of condition and evaluation is assumed by - * the notification object. The main reason for this change in - * behavior is that internal users of this API only use the object - * to use its serialization facilities. - */ - bool owns_elements; }; struct lttng_notification_comm { @@ -57,8 +44,8 @@ struct lttng_notification *lttng_notification_create( struct lttng_evaluation *evaluation); LTTNG_HIDDEN -ssize_t lttng_notification_serialize(struct lttng_notification *notification, - char *buf); +int lttng_notification_serialize(const struct lttng_notification *notification, + struct lttng_dynamic_buffer *buf); LTTNG_HIDDEN ssize_t lttng_notification_create_from_buffer(