From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-91314-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 76147 invoked by alias); 2 Apr 2018 07:51:10 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 76135 invoked by uid 89); 2 Apr 2018 07:51:09 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=Hx-languages-length:415, H*f:sk:2018031, Hurd, month
X-HELO: mx1.redhat.com
Subject: Re: Upstreaming the glibc Hurd port
To: Joseph Myers <joseph@codesourcery.com>,
 Thomas Schwinge <thomas@codesourcery.com>,
 GNU C Library <libc-alpha@sourceware.org>, bug-hurd@gnu.org,
 David Michael <fedora.dm0@gmail.com>
References: <alpine.DEB.2.20.1801182304260.26137@digraph.polyomino.org.uk>
 <20180118235924.r4z4ppvj7xlvmmfp@var.youpi.perso.aquilenet.fr>
 <alpine.DEB.2.20.1801190030000.26137@digraph.polyomino.org.uk>
 <87a7xaupjx.fsf@euler.schwinge.homeip.net>
 <alpine.DEB.2.20.1801191721480.329@digraph.polyomino.org.uk>
 <20180124011051.5s2vugyq3ybnurwc@var.youpi.perso.aquilenet.fr>
 <20180124012726.tibylwp4re5dtgc3@var.youpi.perso.aquilenet.fr>
 <20180125014143.2hxhzon5lzxtqq6j@var.youpi.perso.aquilenet.fr>
 <alpine.DEB.2.20.1801251544550.22734@digraph.polyomino.org.uk>
 <20180319015122.j5tzslkdcnvampoh@var.youpi.perso.aquilenet.fr>
 <20180402001003.3u5n2p5pdmv4hos5@var.youpi.perso.aquilenet.fr>
From: Florian Weimer <fweimer@redhat.com>
Message-ID: <53474635-ce0e-d2a7-3aad-b8dce4426c31@redhat.com>
Date: Mon, 02 Apr 2018 07:51:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180402001003.3u5n2p5pdmv4hos5@var.youpi.perso.aquilenet.fr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2018-04/txt/msg00009.txt.bz2

On 04/02/2018 02:10 AM, Samuel Thibault wrote:
> - elf/check-execstack: We have nested functions which make the stack
>    executable indeed.

I looked at the Hurd situation last month.  Hurd is always 
read-implies-exec, I think.  So there is no need to make the stacks 
executable, it does not have any observable effect on execution and 
therefore cannot be tested.

Thanks,
Florian