From: Radek Madej <radegand@o2.pl>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Please test hardened-sources 2.6.32-r88 and3.2.2
Date: Sat, 28 Jan 2012 20:41:43 +0000 [thread overview]
Message-ID: <5035573.F8iEjxuu0K@quad> (raw)
In-Reply-To: <4F238A74.6020304@opensource.dyc.edu>
On Saturday 28 January 2012 00:41:08 Anthony G. Basile wrote:
> On 01/27/2012 12:38 PM, radegand wrote:
> > Dnia 27 stycznia 2012 17:06 "Tóth Attila"<atoth@atoth.sote.hu>
napisał(a):
> >> And this one is from my laptop:
> >> vmalloc: allocation failure: 0 bytes
> >> modprobe: page allocation failure: order:0, mode:0x80d2
> >> Pid: 3157, comm: modprobe Tainted: G O 3.2.1-hardened #1
>
> >> Call Trace:
> I believe pipacs has fixed this. Please everyone, retest
>
> hardened-sources-2.6.32-r89.ebuild
> hardened-sources-3.2.2-r1.ebuild
>
> I just added them to the tree. I'll rapid stabilize these in about 24
> hours if no one has any issues.
Hi,
I've tested the hardened-sources-3.2.2-r1.ebuild on three different machines,
works like a charm - thanks! :)
Cheers,
Radek
next prev parent reply other threads:[~2012-01-28 20:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 13:37 [gentoo-hardened] Please test hardened-sources 2.6.32-r88 and 3.2.2 Anthony G. Basile
2012-01-27 16:02 ` "Tóth Attila"
2012-01-27 16:06 ` "Tóth Attila"
2012-01-27 17:38 ` [gentoo-hardened] Please test hardened-sources 2.6.32-r88 and3.2.2 radegand
2012-01-28 5:41 ` Anthony G. Basile
2012-01-28 19:21 ` [gentoo-hardened] " 7v5w7go9ub0o
2012-01-28 18:26 ` pageexec
2012-01-28 20:16 ` 7v5w7go9ub0o
2012-01-28 20:46 ` 7v5w7go9ub0o
2012-01-29 10:38 ` Alex Efros
2012-01-29 17:33 ` 7v5w7go9ub0o
2012-01-28 20:41 ` Radek Madej [this message]
2012-01-27 18:18 ` [gentoo-hardened] Re: Please test hardened-sources 2.6.32-r88 and 3.2.2 7v5w7go9ub0o
2012-02-02 20:42 ` [gentoo-hardened] " Tom Hendrikx
2012-02-02 20:47 ` Francisco Blas Izquierdo Riera (klondike)
2012-02-03 2:50 ` Brian Kroth
2012-02-03 12:37 ` Tom Hendrikx
2012-02-03 14:11 ` Tom Hendrikx
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=5035573.F8iEjxuu0K@quad \
--to=radegand@o2.pl \
--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