Bug 531874

Summary: SELinux has prevented vbetool from performing unsafe memory operation
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: vbetoolAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: ajax, dwalsh, jfeeney, mgrepl, mjg59, pknirsch
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-30 10:27:24 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
The report
none
Screenshot showing the load on vbetool
none
gdb of vbetool none

Description Jóhann B. Guðmundsson 2009-10-29 13:37:55 EDT
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 14:18:49 EDT
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 05:30:27 EDT
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 05:31:33 EDT
Created attachment 366774 [details]
Screenshot showing the load on vbetool
Comment 4 Jóhann B. Guðmundsson 2009-10-30 05:58:39 EDT
Created attachment 366776 [details]
gdb of vbetool
Comment 5 Jóhann B. Guðmundsson 2009-10-30 10:18:48 EDT
Note GPU ATI M22 Mobility Radeon X300 and this with "nomodeset" redoing the test with KMS ON...
Comment 6 Matthew Garrett 2009-10-30 10:27:24 EDT
The supported suspend/resume configuration for intel, nvidia and radeon is with KMS enabled, at which point vbetool won't be run.