From: "MOESSBAUER, Felix via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: libbabeltrace2: question about thread safety
Date: Fri, 23 Oct 2026 08:11:17 +0000 [thread overview]
Message-ID: <44074c36528ca4a30909e21072ae67f37b0c244b.camel@siemens.com> (raw)
Hi,
I just noticed that the reference counting in libbabeltrace2 is not
atomic - and by that not thread safe. As I can't know where reference
counting on global objects (like the plugin or component instances) is
done internally, I'm assuming I can't execute two (independent) graphs
in parallel. Some quick tests with tsan seem to confirm my assumption.
Is there any (documented) way to run two graphs in parallel? Or shall
the whole library just be used behind a global mutex?
Best regards,
Felix
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
next reply other threads:[~2026-10-23 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 8:11 MOESSBAUER, Felix via lttng-dev [this message]
2026-11-05 19:48 ` Simon Marchi via lttng-dev
[not found] ` <4b159ade-97af-4008-be23-c81be291f948@simark.ca>
2026-11-06 8:57 ` Moessbauer, Felix via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44074c36528ca4a30909e21072ae67f37b0c244b.camel@siemens.com \
--to=lttng-dev@lists.lttng.org \
--cc=felix.moessbauer@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox