From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: [musl] More thoughts on wrapping signal handling
Date: Thu, 29 Oct 2020 17:02:26 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.20.13.2010291701040.2454@monopod.intra.ispras.ru> (raw)
In-Reply-To: <alpine.LNX.2.20.13.2010291649450.2454@monopod.intra.ispras.ru>
On Thu, 29 Oct 2020, Alexander Monakov wrote:
> On Thu, 29 Oct 2020, Rich Felker wrote:
>
> > Yes, I kinda hand-waved over this with the word "call", which I
> > thought about annotating with (*). In the case of SA_ONSTACK you need
> > a primitive to "call on new stack", and while the ucontext is mostly
> > not meaningful/inspectable to the signal handler (because it's
> > interrupting libc code), the saved signal mask is. You can have the
> > caller restore it (in place of SYS_[rt_]sigreturn), but the natural
> > common solution to all of these needs is having a sort of makecontext.
>
> Alternatively you could re-raise the signal to have the kernel re-deliver
> it with the correctly regenerated ucontext (and on the right stack)?
> Would that be undesirable for some reason?
Ah, because there's no way to propagate siginfo struct. Sorry :)
Alexander
next prev parent reply other threads:[~2020-10-29 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 6:34 Rich Felker
2020-10-29 11:45 ` Alexey Izbyshev
2020-10-29 13:38 ` Rich Felker
2020-10-29 13:51 ` Alexander Monakov
2020-10-29 14:02 ` Alexander Monakov [this message]
2020-10-29 14:12 ` Florian Weimer
2020-10-29 14:18 ` Alexander Monakov
2020-10-29 14:28 ` Rich Felker
2020-10-31 17:33 ` Alexey Izbyshev
2020-10-29 14:21 ` Szabolcs Nagy
2020-10-29 14:43 ` Rich Felker
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=alpine.LNX.2.20.13.2010291701040.2454@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).