From: Anton Blanchard <anton@samba.org>
To: Michael Neuling <mikey@neuling.org>,
Alan Modra <amodra@gmail.com>, Ryan Arnold <ryanarn@us.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: SIGSTKSZ/MINSIGSTKSZ too small on 64bit
Date: Fri, 26 Jul 2013 12:23:25 +1000 [thread overview]
Message-ID: <20130726122325.10b900e4@kryten> (raw)
Hi,
Alan has been looking at a glibc test fail. His analysis shows SEGVs
in signal handlers using sigaltstack, and that MINSIGSTKSZ and SIGSTKSZ
are too small.
We increased the size of rt_sigframe in commit 2b0a576d15e0
(powerpc: Add new transactional memory state to the signal context) but
didn't bump either SIGSTKSZ and MINSIGSTKSZ. We need to do that in both
the kernel and glibc, but I'm a bit worried we could have broken
existing applications that use sigaltstack.
Anton
next reply other threads:[~2013-07-26 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 2:23 Anton Blanchard [this message]
2013-07-26 5:05 ` SIGSTKSZ/MINSIGSTKSZ too small on 64bit Alan Modra
2013-07-26 21:31 ` Ryan Arnold
2013-07-27 1:19 ` Alan Modra
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=20130726122325.10b900e4@kryten \
--to=anton@samba.org \
--cc=amodra@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=ryanarn@us.ibm.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 NNTP newsgroup(s).