All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Graham <douglas.graham@ericsson.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: Setenv/getenv are not thread-safe; whose bug is it?
Date: Mon, 13 Mar 2017 00:21:46 +0000	[thread overview]
Message-ID: <HE1PR07MB09535F02D666D99BB7221713F0250__49028.3827567056$1489364531$gmane$org@HE1PR07MB0953.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <1656612379.3244.1489188755549.JavaMail.zimbra@efficios.com>

> Thanks a lot for the very thorough but report!
> I just prepared a patch for you sent in a separate thread:
> "[PATCH lttng-ust] Fix: race between lttng-ust getenv() and application setenv()"
> Can you give it a try and let me know if it fixes things on your side ?

Thanks for the quick turnaround Mathieu!  

I don't know how we build lttng but I have passed this information along to the team that does, asking that they provide me a library with this patch applied for us to test.  I'll let you know how it looks when we get there.

Regards,
Doug
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2017-03-13  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <HE1PR07MB095321C916B1298B997744F6F0200@HE1PR07MB0953.eurprd07.prod.outlook.com>
2017-03-10 23:32 ` Setenv/getenv are not thread-safe; whose bug is it? Mathieu Desnoyers
     [not found] ` <1656612379.3244.1489188755549.JavaMail.zimbra@efficios.com>
2017-03-13  0:21   ` Douglas Graham [this message]
     [not found]   ` <HE1PR07MB09535F02D666D99BB7221713F0250@HE1PR07MB0953.eurprd07.prod.outlook.com>
2017-03-13  1:12     ` Mathieu Desnoyers
2017-03-10 22:21 Douglas Graham

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='HE1PR07MB09535F02D666D99BB7221713F0250__49028.3827567056$1489364531$gmane$org@HE1PR07MB0953.eurprd07.prod.outlook.com' \
    --to=douglas.graham@ericsson.com \
    --cc=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.