Bug 1125389 - selinux crash when with heavy drm usage
Summary: selinux crash when with heavy drm usage
Keywords:
Status: CLOSED DUPLICATE of bug 1115120
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-31 18:04 UTC by Jason Ekstrand
Modified: 2014-07-31 19:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-31 19:17:52 UTC


Attachments (Terms of Use)
First half of kernel log (1.53 MB, image/jpeg)
2014-07-31 18:04 UTC, Jason Ekstrand
no flags Details
second half of kernel log (1.21 MB, image/jpeg)
2014-07-31 18:04 UTC, Jason Ekstrand
no flags Details

Description Jason Ekstrand 2014-07-31 18:04:16 UTC
Created attachment 923012 [details]
First half of kernel log

Description of problem:
Kernel panics and crashes with "kernel BUG at security/selinux/hooks.c:4511

Version-Release number of selected component (if applicable):
3.16.0-0.rc7.git1.1.fc22

How reproducible:
I can get it to crash at will

Steps to Reproduce:
1. download and build waffle with DRM support
2. download and build piglit
3. run piglit run -p drm quick.py
4. Crash

It also sometimes crashes just by X starting up.  Sometimes, I can't even get a log-in screen.

Actual results:
crash

Expected results:
piglit may report errors, but it shouldn't kernel panic

Additional info:
see attached pictures

Comment 1 Jason Ekstrand 2014-07-31 18:04:42 UTC
Created attachment 923013 [details]
second half of kernel log

Comment 2 Jason Ekstrand 2014-07-31 18:05:47 UTC
It's worth noting that running piglit bangs on drm fairly hard as it is a GL test suite.  However, as I said, I've had it crash under less stress than piglit.

Comment 3 Josh Boyer 2014-07-31 19:17:52 UTC

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


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