Created attachment 310915 [details] emerge --info chromium If CONFIG_PAX_KERNEXEC is enabled in the kernel, and you have chromium running. And then run $ chromium http://gentoo.org/ in a terminal, the system will kernelpanic.
Created attachment 310917 [details] Photo of the kernelpanic
can you post your System.map or vmlinux as well please?
Created attachment 310931 [details] working kernelconfig The System.map file is >1000KB so I can't upload it to the bugtracker. Same with the kernel itself. But this is my kernelconfig, with CONFIG_PAX_KERNEXEC disabled. When I enable CONFIG_PAX_KERNEXEC chromium will panic the kernel. Same setup with CONFIG_PAX_KERNEXEC enabled worked in 3.2.* hardened.
(In reply to comment #3) > The System.map file is >1000KB so I can't upload it to the bugtracker. Same > with the kernel itself. you can try to compress them and/or email them directly to me ;). i really need these files to determine what read-only data was going to be modified.
(In reply to comment #4) > (In reply to comment #3) > > The System.map file is >1000KB so I can't upload it to the bugtracker. Same > > with the kernel itself. > > you can try to compress them and/or email them directly to me ;). i really > need these files to determine what read-only data was going to be modified. http://img.failar.nu/etu/kernel_and_systemmap.tar.bz2
(In reply to comment #5) > http://img.failar.nu/etu/kernel_and_systemmap.tar.bz2 thanks but these files are for 3.3.4, not 3.3.1. i need either the kernel files for the 3.3.1 kernel for which you posted the oops image initially or i need an oops image (or dmesg) for this 3.3.4 kernel.
(In reply to comment #6) > (In reply to comment #5) > > http://img.failar.nu/etu/kernel_and_systemmap.tar.bz2 > > thanks but these files are for 3.3.4, not 3.3.1. i need either the kernel > files for the 3.3.1 kernel for which you posted the oops image initially or > i need an oops image (or dmesg) for this 3.3.4 kernel. http://img.failar.nu/etu/crash_with_3.3.4.tar.bz2 Crashing kernel config, Systemmap, kernel. Emerge --info, and a fresh photo.
(In reply to comment #7) > Crashing kernel config, Systemmap, kernel. Emerge --info, and a fresh photo. cool, now i know that it was this page table being written to: ffffffff817c4000 R level3_vmalloc_end_pgt i'll fix this in the next patch, thanks for your help!
can you test the latest grsec patch? (not sure if they're in hardened already but you can always get it from our site directly)
(In reply to comment #9) > can you test the latest grsec patch? (not sure if they're in hardened > already but you can always get it from our site directly) It will be by this evening if my run tests succeed. hardened-sources-2.6.32-r103 = grsecurity-2.9-2.6.32.59-201205071838 hardened-sources-3.2.16-r2 = grsecurity-2.9-3.2.16-201205071838 hardened-sources-3.3.5 = grsecurity-2.9-3.3.5-201205071839
(In reply to comment #9) > can you test the latest grsec patch? (not sure if they're in hardened > already but you can always get it from our site directly) It works with =sys-kernel/hardened-sources-3.3.5, with CONFIG_PAX_KERNEXEC enabled.
Differently from what the bug title says, I can confirm that even the stable version of hardened-sources (=sys-kernel/hardened-sources-3.2.11) is affected by this bug with both google-chrome and chromium 19.0.1084.56. Upgrading to ~amd64 keyworded version =sys-kernel/hardened-sources-3.3.8, everything works fine.
(In reply to comment #12) > Differently from what the bug title says, I can confirm that even the stable > version of hardened-sources (=sys-kernel/hardened-sources-3.2.11) is > affected by this bug with both google-chrome and chromium 19.0.1084.56. > Upgrading to ~amd64 keyworded version =sys-kernel/hardened-sources-3.3.8, > everything works fine. 3.2.11 is too old to have the fix, i hope 3.2.20+ gets stabilized sooner than later ;).
