From: David Goulet Date: Mon, 3 Jun 2013 17:13:55 +0000 (-0400) Subject: Fix: set metadata closed on a push/close metadata error X-Git-Tag: v2.2.0-rc3~36 X-Git-Url: https://git.lttng.org/?a=commitdiff_plain;h=1b532a6039fbcdb02f698c23e79ee3f607a9790c;hp=1b532a6039fbcdb02f698c23e79ee3f607a9790c;p=lttng-tools.git Fix: set metadata closed on a push/close metadata error Check the metadata closed flag before pushing and closing the metadata on the consumer side. On any error from those two actions, the closed flag is set to indicate to stop using the metadata registry until a destroy is done. Also, before creating a metadata, a check is done to see if the registry metadata was closed previously or else a new metadata key is created and the old values from the previous channel in the registry are used causing a bad state on the consumer. With per UID buffers, the metadata cache is shared accross multiple applications so if the metadata buffers were deleted on the consumer for whatever reasons, we must STOP using it or else undesired behaviors have been observed such as causing synchronization issues between the state of the consumer and sessiond. A destroy session command will wipe the faulty metadata. Acked-by: Mathieu Desnoyers Acked-by: Julien Desfossez Signed-off-by: David Goulet ---