From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Weird coincidental PAX crashes
Date: Sat, 10 May 2014 07:39:01 -0400 [thread overview]
Message-ID: <536E0FD5.2050509@gentoo.org> (raw)
In-Reply-To: <536E0A15.7070603@gentoo.org>
On 05/10/2014 07:14 AM, Joshua Kinard wrote:
>
> I think I ran into this, too, in 3.11. It takes a few days of uptime before
> it happens. Running 3.13.x now on my x64 machine and haven't ran into it
> again. So I second the suggestion to upgrade your kernel.
>
I couldn't come up with a better idea, so last night I upgraded
everything to hardened-sources-3.13.6-r3.
next prev parent reply other threads:[~2014-05-10 11:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 15:15 [gentoo-hardened] Weird coincidental PAX crashes Michael Orlitzky
2014-05-09 15:29 ` Mark Gomersbach
2014-05-09 15:39 ` Michael Orlitzky
2014-05-09 17:46 ` "Tóth Attila"
2014-05-10 11:14 ` Joshua Kinard
2014-05-10 11:39 ` Michael Orlitzky [this message]
2014-05-10 13:43 ` Anthony G. Basile
2014-05-13 19:39 ` Joshua Kinard
2014-05-15 13:11 ` Anthony G. Basile
2014-05-10 16:37 ` Mark Gomersbach
-- strict thread matches above, loose matches on Subject: below --
2014-05-15 13:48 PaX Team
2014-05-15 15:22 ` Michael Orlitzky
2014-05-15 13:49 PaX Team
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=536E0FD5.2050509@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-hardened@lists.gentoo.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