From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-99189-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 95172 invoked by alias); 11 Jan 2019 20:06:41 -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 95161 invoked by uid 89); 11 Jan 2019 20:06:41 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*Ad:D*io
X-HELO: mail-ed1-f47.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=brauner.io; s=google;
        h=date:user-agent:in-reply-to:references:mime-version
         :content-transfer-encoding:subject:to:cc:from:message-id;
        bh=JCTMleffxbErC0hsRVPWYcYt41ocK86peCOHk7TWUBU=;
        b=WTaAhZkSxN2yQNOFLBHeRQxhFl9tk8JTZShRlNljWB/VigCLc3tNjJ70Bic4KHnyrC
         rkvOPJI5qkY+bxIvC51bFkvhF0R3iUUGGze1Nul90xDDQ4MAK2DKE3sBlAzRZiFDr5wF
         WEKaasQ8EkNkVeRZA4V44lPMU9VfRhTfbLndFJxMlqNC8iD7lBq8w4GF1FHKipwpT962
         XUcDL2pL5GxIYE7nSjFKECly7EpabDjj2/++ik/i1gPm3I2ynFm0aDXvFXa1/CUo1MMu
         BdBlbGAnDSMOK0GhMPx9+O6j6efQA+N0ClrBjITdZ17wkejoxCPZesXGlrGYJ3CHojSF
         3fnA==
Return-Path: <christian@brauner.io>
Date: Fri, 11 Jan 2019 20:06:00 -0000
User-Agent: K-9 Mail for Android
In-Reply-To: <874lafezhe.fsf@oldenburg2.str.redhat.com>
References: <e4215c6e-e8a4-a9b6-d88f-3c54e262711a@redhat.com> <CAKCAbMiCaBst_ofjKkH3Ck1CoOV86wPKv3QSkC89XW_zu=1BLA@mail.gmail.com> <CAKCAbMiWEk6UZJZPQb9h6GOJ5tWACMUzgg5dUra0ET4bESMotQ@mail.gmail.com> <874lafezhe.fsf@oldenburg2.str.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: Fwd: What can a signal handler do with SIGSTKSZ?
To: libc-alpha@sourceware.org,Florian Weimer <fweimer@redhat.com>,Zack Weinberg <zackw@panix.com>
CC: GNU C Library <libc-alpha@sourceware.org>
From: Christian Brauner <christian@brauner.io>
Message-ID: <C2747F17-C976-462B-B491-F53A502D8E3B@brauner.io>
X-SW-Source: 2019-01/txt/msg00259.txt.bz2

On January 11, 2019 9:00:29 PM GMT+01:00, Florian Weimer <fweimer@redhat.co=
m> wrote:
>* Zack Weinberg:
>
>> Now, if 8192 bytes is not enough to call some async-signal-safe
>> functions, that's another problem and one I would like to see
>> addressed by making the unwind library more space-efficient or
>> something along those lines.
>
>Small nit: This is unrelated to async-signal-safe functions because
>size
>considerations also apply to synchronously delivered signals, where few
>(if any) restrictions exist.
>
>Thanks,
>Florian

Does this need kernel-side input?
Should we move parts of this to lkml or at least Cc a few people (Oleg, And=
y, Eric)?
Just checking. :)

Thanks!
Christian