From: Stas Sergeev <stsp@list.ru>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>, wharms@bfs.de
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: Mon, 30 Oct 2017 13:58:11 +0300 [thread overview]
Message-ID: <d6974f33-cfdb-fdbc-8d8a-1b3dc43d6ee0@list.ru> (raw)
In-Reply-To: <a8ae5fc2-055c-2939-a692-2339398bf653@gmail.com>
30.10.2017 13:50, Michael Kerrisk (man-pages) пишет:
> I see what you mean. The point is back then that SS_ONSTACK was
> the only flag that could (on Linux) be specified in ss.ss_flags,
> so that "SS_ONSTACK | SOMETHING_FLAG" was a nonexistent case.
> These days, it's possible to specify the new SS_AUTODISARM
> flag in ss.ss_flags, which I think is why you are doubtful
> about the new page text. How about this, as a tightened-up
> version:
>
> BUGS
> In Linux 2.2 and earlier, the only flag that could be specified in
> ss.sa_flags was SS_DISABLE. In the lead up to the release of the
> Linux 2.4 kernel, a change was made to allow sigaltstack() to
> allow ss.ss_flags==SS_ONSTACK with the same meaning as
> ss.ss_flags==0 (i.e., the inclusion of SS_ONSTACK in ss.ss_flags
> is a no-op). On other implementations, and according to POSIX.1,
> SS_ONSTACK appears only as a reported flag in old_ss.ss_flags. On
> Linux, there is no need ever to specify SS_ONSTACK in ss.ss_flags,
> and indeed doing so should be avoided on portability grounds: var‐
> ious other systems give an error if SS_ONSTACK is specified in
> ss.ss_flags.
>
And after all these amendments it seems to
no longer belong to BUGS section but to NOTES.
next prev parent reply other threads:[~2017-10-30 11:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 20:38 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
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 [this message]
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=d6974f33-cfdb-fdbc-8d8a-1b3dc43d6ee0@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 \
--cc=wharms@bfs.de \
/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
all inboxes | Powered by JetHome®