Bug 531874 - SELinux has prevented vbetool from performing unsafe memory operation
Summary: SELinux has prevented vbetool from performing unsafe memory operation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vbetool
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-29 17:37 UTC by Jóhann B. Guðmundsson
Modified: 2013-01-10 08:03 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-30 14:27:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The report (2.61 KB, text/plain)
2009-10-29 17:37 UTC, Jóhann B. Guðmundsson
no flags Details
Screenshot showing the load on vbetool (1.76 MB, image/png)
2009-10-30 09:31 UTC, Jóhann B. Guðmundsson
no flags Details
gdb of vbetool (11.62 KB, text/plain)
2009-10-30 09:58 UTC, Jóhann B. Guðmundsson
no flags Details

Description Jóhann B. Guðmundsson 2009-10-29 17:37:55 UTC
Created attachment 366669 [details]
The report 

Description of problem:

See attache file for details. 

Note I was not offered to report this through SELinux Gui however I was offered to turn off memory protection.

I left the laptop suspended ( closed the lid ) overnight and I think this is the cause for the gui not return after staying suspended for so long ( all I got was a black screen with the mouse pointer keyboard was responding and switching to tty2 work fine and switching back to tty1 ( desktop ) still gave me black screen with only the mouse pointer visible.. then again this all might be a xorg-x11-drv-ati issue note this only seems to happen when the laptop has been suspended for a long period of time.. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Daniel Walsh 2009-10-29 18:18:49 UTC
There is an effort to remove the need for mmap_zero from vbetool.  For now set the boolean and see if suspend/resume works correctly.

Comment 2 Jóhann B. Guðmundsson 2009-10-30 09:30:27 UTC
Uhum it did return after a while with vbetool hogging the cpu. 

It's been running like that for quite a while now which makes one wonder if vbetool is looping..

Comment 3 Jóhann B. Guðmundsson 2009-10-30 09:31:33 UTC
Created attachment 366774 [details]
Screenshot showing the load on vbetool

Comment 4 Jóhann B. Guðmundsson 2009-10-30 09:58:39 UTC
Created attachment 366776 [details]
gdb of vbetool

Comment 5 Jóhann B. Guðmundsson 2009-10-30 14:18:48 UTC
Note GPU ATI M22 Mobility Radeon X300 and this with "nomodeset" redoing the test with KMS ON...

Comment 6 Matthew Garrett 2009-10-30 14:27:24 UTC
The supported suspend/resume configuration for intel, nvidia and radeon is with KMS enabled, at which point vbetool won't be run.


Note You need to log in before you can comment on or make changes to this bug.