Summary: | sys-kernel/hardened-sources-2.6.28-r9: Many modules including ip_tables break with PAX_KERNEXEC FATAL: Error inserting ipt_REJECT (Cannot allocate memory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dillon <developer> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Kernel Team (OBSOLETE) <hardened-kernel+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kernel Config file that produces module errors
Functional config file diff of the Changes between the functional and non-functional config file Log of shorewall failing to initialize leaving no netfilter rules established (open firewall) |
Description
Dillon
2009-07-31 02:23:01 UTC
Created attachment 199693 [details]
kernel Config file that produces module errors
Created attachment 199695 [details]
Functional config file
Created attachment 199696 [details, diff]
diff of the Changes between the functional and non-functional config file
Created attachment 199698 [details]
Log of shorewall failing to initialize leaving no netfilter rules established (open firewall)
We are working towards stabilizing 2.6.32-r9 for x86. Its already stable for amd64. Can the reporter try 2.6.32-r9 since the required SELinux patch should already have been applied. (In reply to comment #5) > We are working towards stabilizing 2.6.32-r9 for x86. Its already stable for > amd64. Can the reporter try 2.6.32-r9 since the required SELinux patch should > already have been applied. > I've been using 2.6.32-hardened-r9 for several months now without issue, should this be RESOLVED FIXED? (In reply to comment #6) > (In reply to comment #5) > > We are working towards stabilizing 2.6.32-r9 for x86. Its already stable for > > amd64. Can the reporter try 2.6.32-r9 since the required SELinux patch should > > already have been applied. > > > > I've been using 2.6.32-hardened-r9 for several months now without issue, should > this be RESOLVED FIXED? > Yes. |