First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 177387
Alias:
Product:
Component:
Status: RESOLVED
Resolution: TEST-REQUEST
Assigned To: The Gentoo Linux Hardened Team <hardened@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Yaroslav Isakov <yaroslav.isakov@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
emerg.info emerge --info output text/plain Yaroslav Isakov 2007-05-06 23:56 0000 3.73 KB Details
logz excerpt from syslog with error text/plain Yaroslav Isakov 2007-05-06 23:57 0000 1.59 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 177387 depends on: Show dependency tree
Bug 177387 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-05-06 23:54 0000 
I launch qemu-0.9.0 with modprobe'd kqemu-1.3.0-pre11 and it crashed with this
message in syslog:
PAX: suspicious general protection fault: 0000 [#1]
When I disable PAX_KERNEXEC in hardened-sources-2.6.20-r2, it works as intended
(no crashes)

------- Comment #1 From Yaroslav Isakov 2007-05-06 23:56:11 0000 ------- 
Created an attachment (id=118390) [details]
emerge --info output

BTW, I use gcc-3.4.6-r2 to compile qemu-user and qemu-softmmu

------- Comment #2 From Yaroslav Isakov 2007-05-06 23:57:46 0000 ------- 
Created an attachment (id=118392) [details]
excerpt from syslog with error

------- Comment #3 From Kevin F. Quinn (RETIRED) 2007-05-07 11:21:24 0000 ------- 

*** This bug has been marked as a duplicate of bug 177234 ***

------- Comment #4 From PaX Team 2007-05-07 23:05:43 0000 ------- 
(In reply to comment #3)
> 
> *** This bug has been marked as a duplicate of bug 177234 ***

i think it's a genuine issue, the other bug is related to grsecurity itself,
not PaX, while here we're seeing something triggered by KERNEXEC. what i'd like
to see is a decoded oops however.

------- Comment #5 From solar 2007-05-07 23:13:04 0000 ------- 
Reopening bug

------- Comment #6 From Luca Barbato 2009-03-07 15:47:43 0000 ------- 
Please check the new release.
First Last Prev Next    No search results available      Search page      Enter new bug