From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753246AbdJ3Ln1 (ORCPT ); Mon, 30 Oct 2017 07:43:27 -0400 Received: from fallback12.m.smailru.net ([94.100.179.29]:49144 "EHLO fallback.mail.ru" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752249AbdJ3LnZ (ORCPT ); Mon, 30 Oct 2017 07:43:25 -0400 X-Greylist: delayed 2694 seconds by postgrey-1.27 at vger.kernel.org; Mon, 30 Oct 2017 07:43:25 EDT Subject: Re: Documenting sigaltstack SS_AUTODISRM To: "Michael Kerrisk (man-pages)" , wharms@bfs.de Cc: linux-man , Andy Lutomirski , Oleg Nesterov , lkml References: <08467ae1-7187-3b2a-9a78-8af0c10bf816@list.ru> <3907bc2a-0645-8d93-6ee5-3f99874e7022@gmail.com> <32d95303-5839-9279-a1d3-a06f34e3484e@list.ru> <50de8f3b-8a1e-df50-b5dd-d1b74cb77fad@list.ru> <026308b5-4e92-4439-1eb2-82b67584d548@gmail.com> <3a4f9f3e-fc33-cf98-2322-27087664813f@list.ru> <59F6FD39.40502@bfs.de> From: Stas Sergeev Message-ID: Date: Mon, 30 Oct 2017 13:58:11 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-MW X-7FA49CB5: 0D63561A33F958A506AAED145C5342382E64DB15C9B38C1D05A48EB79A94CF5F725E5C173C3A84C309A7649CC036878F1DC778750C4E5D9B1D6A3D1828C120DEC4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F41B67924A99884D73B503F486389A921A5CC5B56E945C8DA X-Mailru-Sender: 262249EAF8EF1149DD59B264A707D22416BE4A25B51FEA668B45D187AA2645607A7473263BB6639E1653177920737CA72999BEE114A20FF4278B2D54D4112F244F0A872F021F905956A8FB0C6EBA5FCCEAB4BC95F72C04283CDA0F3B3F5B9367 X-Mras: OK X-7FA49CB5: 0D63561A33F958A5996845F3A8708B1E57FFC193313EDAA031EA771C1C80E9DC462275124DF8B9C938130EB80001CEACE5BFE6E7EFDEDCD789D4C264860C145E X-Mailru-Sender: A5480F10D64C900521F65ACE11A97E3DB2606819D843B418991A091707C5737CA82939391C8226F2BD9A213A94BF4775DDBB79867CC2C1EC5DD9ADBE8243F6ED0252A3EF2865ED2F733E9BFD465368085FEEDEB644C299C0ED14614B50AE0675 X-Mras: OK Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.