lttng: Don't build trace headers when lttng is disabled

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Remove -lboost_regex from unit test

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Fix build error on 32-bit systems

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Don't build trace libraries when lttng is disabled

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Test for sane lttng-gen-tp

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Check that the main babeltrace header is present

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Check for babeltrace when autoconfiguring lttng

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Only install rbd-replay-prep when enabled

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Add informational messages to configure.ac

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Remove tracing-specfic local variables when lttng disabled

Signed-off-by: Adam Crume <adamcrume@gmail.com>
lttng: Split --with-lttng and --with-babeltrace options

Signed-off-by: Adam Crume <adamcrume@gmail.com>
rbd-replay: Add unit test for Ser

Signed-off-by: Adam Crume <adamcrume@gmail.com>
rbd_replay: Add unit test for batch_unreachable_from

This requires a fair amount of code reorganization, since the types in
the function signature were previously not in a header file.

Signed-off-by: Adam Crume <adamcrume@gmail.com>
mon: add a cluster fingerprint

Generate it on cluster creations with the initial monmap.  Include it in
the report.  Provide no way for this uuid to be fed in to the cluster
(intentionally or not) so that it can be assumed to be a truly unique
identifier for the cluster.

Signed-off-by: Sage Weil <sage@redhat.com>
mon: generate cluster_fingerprint if null

This triggers after an upgrade of a legacy cluster that has no fingerprint.

Signed-off-by: Sage Weil <sage@redhat.com>
mon: fix occasional message leak after session reset

Consider:

 - we get a message, put it on a wait list
 - the client session resets
 - we go back to process the message later and discard
   - _ms_dispatch returns false, but nobody drops the msg ref

Since we call _ms_dispatch() a lot internally, we need to always return
true when we are an internal caller.

Fixes: #9176
Backport: firefly, dumpling
Signed-off-by: Sage Weil <sage@redhat.com>
mon: always process the message in dispatch

Nobody should be chained after teh mon, so we can safely drop any message
we don't understand.

Signed-off-by: Sage Weil <sage@redhat.com>
mon: make dispatch(), _ms_dispatch() void

They always return true.

Signed-off-by: Sage Weil <sage@redhat.com>
Merge pull request #2253 from adamcrume/wip-lttng

RBD-replay

Reviewed-by: Sage Weil <sage@redhat.com>
Merge pull request #2274 from ceph/wip-9144

filestore: fix force_sync race with mount + umount + mount

Reviewed-by: David Zafman <dzafman@redhat.com>