From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Nick Alcock <nix@esperi.org.uk>, linux-kernel@vger.kernel.org
Cc: Sparc kernel list <sparclinux@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Florian Weimer <fweimer@redhat.com>,
"Jose E. Marchesi" <jose.marchesi@oracle.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: Fri, 27 May 2016 15:34:32 +0200 [thread overview]
Message-ID: <33bce6ca-696c-9ec4-2567-83fed24323c3@physik.fu-berlin.de> (raw)
In-Reply-To: <87twhj3ag0.fsf@esperi.org.uk>
Hi Nick!
On 05/27/2016 03:19 PM, Nick Alcock wrote:
> So I've been working on a patch series (see below) that applies GCC's
> -fstack-protector{-all,-strong} to almost all of glibc bar the dynamic
> linker. In trying to upstream it, one review commenter queried one
> SPARC-specific patch in the series; the absence of this patch triggers a
> BUG in the SPARC kernel when glibc is tested as an unprivileged user, on
> all versions tested from Oracle UEK 4.1 right up to 4.6.0, at least on
> the ldoms I have access to and presumably on bare hardware too.
I apologize for hijacking this thread but since you are mentioning glibc,
there are actually a couple of tests in the glibc testsuite [1].
Jose Marchesi has started looking at them and most of them seem to be
related to unaligned accesses. Would be great if those could be resolved
in the near future, too.
We're working towards getting Debian's sparc64 port into a releasable
state, but there are some packages like glibc or util-linux that need
work since their testsuites fail.
Cheers,
Adrian
> [1] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.22-9&stamp=1464023539
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2016-05-27 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 11:17 [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 Nick Alcock
2016-05-27 13:19 ` Nick Alcock
2016-05-27 13:34 ` John Paul Adrian Glaubitz [this message]
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
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=33bce6ca-696c-9ec4-2567-83fed24323c3@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=davem@davemloft.net \
--cc=fweimer@redhat.com \
--cc=jose.marchesi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).