From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-99348-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 18580 invoked by alias); 16 Jan 2019 22:47:18 -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 18550 invoked by uid 89); 16 Jan 2019 22:47:17 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=H*RU:209.85.215.193, Hx-spam-relays-external:209.85.215.193, H*Ad:U*rth, H*r:sk:mail-pg
X-HELO: mail-pg1-f193.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=sender:subject:to:cc:references:from:openpgp:autocrypt:message-id
         :date:user-agent:mime-version:in-reply-to:content-language
         :content-transfer-encoding;
        bh=j4l1G6RpoMdxN3hYqJMEyj4yl104DYBQX14IyJ9WPN4=;
        b=K1JGdKIoVpWZ5PSHd/bR4sWxHdkqS0toaJrju7f0r67BPB2el3kVLh5T8q/+9IArCi
         8j4h/xeBpUDheabBXtc09bG7rb0dvL9jSNyETDgSOmHNWiaqE4NcpkO6AiA7MR/ASEvZ
         B+0dieREmrlXs+8eHjnWKEC13khxuXEytEKSNNfGBprefDtkkjYTvq6fstiD5nE4XLQl
         3TJ7b5dv9NIrpCVs+3iHF3qcjSf7X6ymGvdyJcHxK02MFo2dxT42/HTzOCGF5O07FC4i
         BfQpnXXeHs8s52N7DefW7fvQAvGxBTzIJvKafzgcGA+0H/PJQt+KYhYPKwU4yGc8zGSr
         J7iQ==
Return-Path: <rth7680@gmail.com>
Sender: Richard Henderson <rth7680@gmail.com>
Subject: Re: [PATCH] Tests for minimal signal handler functionality in
 MINSIGSTKSZ space.
To: Carlos O'Donell <carlos@redhat.com>, Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
 Siddhesh Poyarekar <siddhesh@gotplt.org>
References: <20190115200526.4677-1-zackw@panix.com>
 <1d45c6cb-192c-5ade-513e-a40c65d9fb7e@redhat.com>
 <CAKCAbMhSxEznwJDjSscq_whWk8j8TV409HAgGJ4AGOrHhV=8bw@mail.gmail.com>
 <dfefe1c3-7952-9878-757d-48a15c880332@redhat.com>
 <CAKCAbMiaUYOLkRD36MEVJRuzbAyjC7DEYNz68ZuJdWDrq=YPRQ@mail.gmail.com>
 <35b94b4d-adaa-7a83-a357-d82d6b4b2249@redhat.com>
From: Richard Henderson <rth@twiddle.net>
Openpgp: preference=signencrypt
Message-ID: <089ec328-7d41-2afb-559c-d13c4a6d9f69@twiddle.net>
Date: Wed, 16 Jan 2019 22:47:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <35b94b4d-adaa-7a83-a357-d82d6b4b2249@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SW-Source: 2019-01/txt/msg00418.txt.bz2

On 1/17/19 4:06 AM, Carlos O'Donell wrote:
> I worried about this during the original review, but my conclusion was
> that no sane user would do such an alignment to push their own stack
> against the guard. At least I've never seen it done.

I have seen users use malloc to allocate stacks.  Which is basically the same
as putting the allocation next to the guard, except it corrupts the arena
instead.  :-P


r~