From: Nix <nix@esperi.org.uk>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
fweimer@redhat.com
Subject: Re: [4.1.x -- 4.6.x and probably HEAD] Reproducible unprivileged panic/TLB BUG on sparc via a stack-protected rt_sigaction() ka_restorer, courtesy of the glibc testsuite
Date: Mon, 30 May 2016 13:43:01 +0100 [thread overview]
Message-ID: <878tyrvhre.fsf@esperi.org.uk> (raw)
In-Reply-To: <20160528.230250.216567426920998466.davem@davemloft.net> (David Miller's message of "Sat, 28 May 2016 23:02:50 -0700 (PDT)")
On 29 May 2016, David Miller spake thusly:
> BTW Nick, in thinking through all of this, I want to strongly encourage
> you to disable stack protector for all sigreturn stubs in the GLIBC tree.
I completely concur, and have already written (but not committed) a
patch to do this: I'll augment the existing sparc-only patch into a
sigreturn-stubs patch. I *think* I spotted all the stubs. (Many of them
are in assembler, but not all.)
(If there's anything else which involves calling functions with a
precisely-aligned stack and an expectation of no stack pointer movement
in the prologue or epilogue, I'd be interested to know about it, since
that'll need inhibit_stack_protector'ing too.)
--
NULL && (void)
prev parent reply other threads:[~2016-05-30 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 11:17 Nick Alcock
2016-05-27 13:19 ` Nick Alcock
2016-05-27 13:34 ` John Paul Adrian Glaubitz
2016-05-27 13:43 ` Nick Alcock
2016-05-27 19:37 ` David Miller
2016-05-27 21:44 ` Nick Alcock
2016-05-27 22:51 ` David Miller
2016-05-29 4:24 ` David Miller
2016-05-29 17:30 ` Sam Ravnborg
2016-05-30 2:15 ` David Miller
2016-05-29 6:02 ` David Miller
2016-05-30 12:43 ` Nix [this message]
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=878tyrvhre.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=davem@davemloft.net \
--cc=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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
all inboxes | Powered by JetHome®