From: Al Viro <viro@zeniv.linux.org.uk>
To: Stas Sergeev <stsp@list.ru>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC][possible bug] when should SS_AUTODISARM have effect?
Date: Thu, 19 Mar 2020 02:16:29 +0000 [thread overview]
Message-ID: <20200319021629.GC23230@ZenIV.linux.org.uk> (raw)
Consider the following scenario: SIGPIPE has SA_ONSTACK
handler, SIGSEGV - non-SA_ONSTACK one. SIGPIPE is delivered
and we fail halfway through setting a sigframe for it.
OK, we get SIGSEGV forced in, which gets handled not on altstack.
But what should happen if we fail *after* having saved the
altstack settings into the sigframe that got abandoned?
AFAICS, we get them reset and the original setting
entirely lost. Shouldn't that thing be applied only after
we have succeeded in building the frame? In signal_delivered(),
perhaps...
I realize that this is out of scope for POSIX, so it's
not a matter of standard compliance, but it looks like a bit
of a QoI issue...
next reply other threads:[~2020-03-19 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 2:16 Al Viro [this message]
2020-03-21 17:59 ` [RFC][possible bug] when should SS_AUTODISARM have effect? Andy Lutomirski
2020-03-21 22:24 ` stsp
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=20200319021629.GC23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stsp@list.ru \
/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 NNTP newsgroup(s).