linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@list.ru>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Oleg Nesterov <oleg@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Documenting sigaltstack SS_AUTODISRM
Date: Thu, 25 May 2017 12:17:07 +0300	[thread overview]
Message-ID: <3a4f9f3e-fc33-cf98-2322-27087664813f@list.ru> (raw)
In-Reply-To: <026308b5-4e92-4439-1eb2-82b67584d548@gmail.com>

24.05.2017 14:09, Michael Kerrisk (man-pages) пишет:
> One could do this I suppose, but I read POSIX differently from
> you and, more importantly, SS_ONSTACK breaks portability on
> numerous other systems and is a no-op on Linux. So, the Linux man
> page really should warn against its use in the strongest terms.
So how about instead of the strongest terms towards
the code's author, just explain that SS_ONSTACK is a
bit-value on some/many OSes, and as such, 0 is a
valid value to enable sas on them, plus all the other
values would give EINVAL?
No strongest terms will help w/o an explanation,
because people will keep looking for something that
suits as a missing SS_ENABLE.

  parent reply	other threads:[~2017-05-25  9:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 20:38 Documenting sigaltstack SS_AUTODISRM Michael Kerrisk (man-pages)
2017-05-22 23:36 ` Stas Sergeev
2017-05-23 10:35   ` Michael Kerrisk (man-pages)
2017-05-23 11:03     ` Stas Sergeev
2017-05-23 12:26       ` Michael Kerrisk (man-pages)
2017-05-23 23:01         ` Stas Sergeev
2017-05-24 11:09           ` Michael Kerrisk (man-pages)
2017-05-24 20:12             ` Stas Sergeev
2017-10-30 12:38               ` Michael Kerrisk (man-pages)
2017-11-06 22:26                 ` Michael Kerrisk (man-pages)
2017-11-06 22:28                   ` Stas Sergeev
2017-11-08  7:41                     ` Michael Kerrisk (man-pages)
2017-05-25  9:17             ` Stas Sergeev [this message]
2017-10-30 10:04               ` Michael Kerrisk (man-pages)
2017-10-30 10:21                 ` walter harms
2017-10-30 10:50                   ` Michael Kerrisk (man-pages)
2017-10-30 10:58                     ` Stas Sergeev
2017-10-30 12:54                     ` walter harms

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=3a4f9f3e-fc33-cf98-2322-27087664813f@list.ru \
    --to=stsp@list.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mtk.manpages@gmail.com \
    --cc=oleg@redhat.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;
as well as URLs for NNTP newsgroup(s).