All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Tolga Dalman <tolga.dalman-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mcheck(3): add a notice that the current implementation is not thread-safe
Date: Wed, 06 May 2015 07:05:53 +0200	[thread overview]
Message-ID: <5549A131.5020404@gmail.com> (raw)
In-Reply-To: <5408D288.1050407-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>

Hello Toga,

On 09/04/2014 10:58 PM, Tolga Dalman wrote:
> Hello Michael,
> 
> mcheck is known to be unusable for quite some time with multi-threaded
> applications:
> 
> 	https://sourceware.org/bugzilla/show_bug.cgi?id=9939
> 
> Until yesterday (including many hours of bug-hunting) this fact was not
> known to me, thus, I would like to suggest to add a note in the mcheck(3) manual
> page (and probably in the GLIBC documentation as well). I think one sentence in
> the NOTES section should suffice.

It is sometime since your mail, but FYI, notes on the thread-non-safety of 
mcheck() were added to the page in the last months.

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2015-05-06  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 20:58 mcheck(3): add a notice that the current implementation is not thread-safe Tolga Dalman
     [not found] ` <5408D288.1050407-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2015-05-06  5:05   ` Michael Kerrisk (man-pages) [this message]

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=5549A131.5020404@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tolga.dalman-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
    /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.