Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: paul_woegerer@mentor.com (Paul Woegerer)
Subject: [lttng-dev] [PATCH lttng-ust 2/3] Fix: baddr_statedump deadlock with JUL tracing
Date: Thu, 28 Nov 2013 13:26:53 +0100	[thread overview]
Message-ID: <1385641614-18806-3-git-send-email-paul_woegerer@mentor.com> (raw)
In-Reply-To: <1385641614-18806-1-git-send-email-paul_woegerer@mentor.com>

Signed-off-by: Paul Woegerer <paul_woegerer at mentor.com>
---
 liblttng-ust/lttng-ust-comm.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/liblttng-ust/lttng-ust-comm.c b/liblttng-ust/lttng-ust-comm.c
index 2d3766f..0c7fc65 100644
--- a/liblttng-ust/lttng-ust-comm.c
+++ b/liblttng-ust/lttng-ust-comm.c
@@ -1214,10 +1214,12 @@ restart:
 			if (ret) {
 				ERR("Error handling message for %s socket", sock_info->name);
 			} else {
+				int ctor_passed;
 				struct lttng_session *session;
 
+				ctor_passed = sock_info->constructor_sem_posted;
 				session = sock_info->session_enabled;
-				if (session) {
+				if (ctor_passed && session) {
 					sock_info->session_enabled = NULL;
 					lttng_ust_baddr_statedump(session);
 				}
-- 
1.8.4




  parent reply	other threads:[~2013-11-28 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 12:26 [lttng-dev] [PATCH lttng-ust 0/3] Solve remaining issues with base-address-state tracing Paul Woegerer
2013-11-28 12:26 ` [lttng-dev] [PATCH lttng-ust 1/3] Integrate base-address statedump into lttng-ust Paul Woegerer
2013-11-28 12:26 ` Paul Woegerer [this message]
2013-11-28 12:26 ` [lttng-dev] [PATCH lttng-ust 3/3] Allow suppressing of base-address-state tracing Paul Woegerer
2013-11-28 15:59 ` [lttng-dev] [PATCH lttng-ust 0/3] Solve remaining issues with " Mathieu Desnoyers

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=1385641614-18806-3-git-send-email-paul_woegerer@mentor.com \
    --to=paul_woegerer@mentor.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