From: Christian Brauner <christian@brauner.io>
To: libc-alpha@sourceware.org,Florian Weimer
<fweimer@redhat.com>,Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Fwd: What can a signal handler do with SIGSTKSZ?
Date: Fri, 11 Jan 2019 20:06:00 -0000 [thread overview]
Message-ID: <C2747F17-C976-462B-B491-F53A502D8E3B@brauner.io> (raw)
In-Reply-To: <874lafezhe.fsf@oldenburg2.str.redhat.com>
On January 11, 2019 9:00:29 PM GMT+01:00, Florian Weimer <fweimer@redhat.com> 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, Andy, Eric)?
Just checking. :)
Thanks!
Christian
next prev parent reply other threads:[~2019-01-11 20:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 17:44 Carlos O'Donell
2019-01-11 19:02 ` Szabolcs Nagy
2019-01-11 19:11 ` Carlos O'Donell
2019-01-11 20:23 ` Szabolcs Nagy
[not found] ` <CAKCAbMiCaBst_ofjKkH3Ck1CoOV86wPKv3QSkC89XW_zu=1BLA@mail.gmail.com>
2019-01-11 19:34 ` Fwd: " Zack Weinberg
2019-01-11 20:00 ` Florian Weimer
2019-01-11 20:06 ` Christian Brauner [this message]
2019-01-11 20:14 ` Florian Weimer
2019-01-11 20:26 ` Christian Brauner
2019-01-14 16:15 ` Florian Weimer
2019-01-11 20:09 ` Zack Weinberg
2019-01-11 20:29 ` Florian Weimer
2019-01-11 23:59 ` Zack Weinberg
2019-01-14 11:18 ` Szabolcs Nagy
2019-01-14 11:29 ` Adhemerval Zanella
2019-01-14 16:34 ` Zack Weinberg
2019-01-14 20:29 ` Carlos O'Donell
2019-01-14 16:18 ` Florian Weimer
2019-01-14 16:23 ` Carlos O'Donell
2019-01-14 16:31 ` Florian Weimer
2019-01-14 16:34 ` Szabolcs Nagy
2019-01-14 18:19 ` Joseph Myers
2019-01-14 20:30 ` Carlos O'Donell
2019-01-16 22:51 ` Christian Brauner
2019-01-11 19:40 ` Florian Weimer
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=C2747F17-C976-462B-B491-F53A502D8E3B@brauner.io \
--to=christian@brauner.io \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).