Linux Manual Pages development
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
Subject: Re: [PATCH] signal.7: add missing async-signal-safe functions
Date: Fri, 11 Sep 2015 13:28:28 +0200	[thread overview]
Message-ID: <20150911112828.GG3417@dhcp22.suse.cz> (raw)
In-Reply-To: <55F2B413.5090003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri 11-09-15 12:59:31, Michael Kerrisk wrote:
> Hi Michael,
> 
> On 09/07/2015 05:07 PM, mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org wrote:
> > From: Michal Hocko <mhocko-IBi9RG/b67k@public.gmane.org>
> > 
> > It seems that few async-signal-safe functions listed by POSIX.1-2008
> > http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_04_03
> > are not mentioned in the man page. I am not exactly sure in which
> > version of the standard they have declared as signal safe. So they
> > were added to the section according to which standard they conform to:
> > 
> > POSIX.1-2001
> > - fchdir
> > - pthread_self
> > - pthread_sigmask
> > 
> > POSIX.1-2008
> > - pthread_kill
> 
> Thanks for spotting this. I had missed it myself.
> I see now that those 4 functions were added in POSIX.1-2008
> Technical Corrigendum 1 (2013). So, I've applied a different
> patch (below). Thanks for catching this, and the effort on the
> patch.

OK, thanks for fixing that up!
-- 
Michal Hocko
SUSE Labs
--
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-09-11 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 15:07 [PATCH] signal.7: add missing async-signal-safe functions mhocko-DgEjT+Ai2ygdnm+yROfE0A
     [not found] ` <1441638469-22062-1-git-send-email-mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-09-11 10:59   ` Michael Kerrisk (man-pages)
     [not found]     ` <55F2B413.5090003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-11 11:28       ` Michal Hocko [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=20150911112828.GG3417@dhcp22.suse.cz \
    --to=mhocko-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=tiwai-l3A5Bk7waGM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox