Bug 866497 - missing NULL check in audit_log_link_denied
Summary: missing NULL check in audit_log_link_denied
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-15 13:54 UTC by Tom Horsley
Modified: 2013-01-02 17:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-02 17:17:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
photo of oops that appeared on the screen (473.36 KB, image/jpeg)
2012-10-15 13:54 UTC, Tom Horsley
no flags Details

Description Tom Horsley 2012-10-15 13:54:09 UTC
Created attachment 627448 [details]
photo of oops that appeared on the screen

Description of problem:

I installed the latest updates this morning and rebooted to get the 3.6.1 kernel loaded. After using the system for a bit, I got the kernel OOPS I will attach a photo of.

The oops was very sudden, and when it happened, I was trying to connect an android device to my local subnet created via hostapd on my f17 desktop. I mention that since I see dhcpd mentioned in the OOPS.

I also see audit mentioned in the OOPS, and I was running with the audit=0 kernel command line option. When rebooting, I removed that and enabled the auditd service, so I'll see if I get another oops with audit running.


Version-Release number of selected component (if applicable):
kernel-3.6.1-1.fc17.x86_64

How reproducible:
Just once so far.

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:
sudden oops

Expected results:
sustem keeps working

Additional info:

Comment 1 Dave Jones 2012-10-17 19:22:42 UTC
this should be fixed upstream in commit d1c7d97ad58836affde6e39980b96527510b572e
I'll point it out for the stable maintainers.

Comment 2 Tom Horsley 2012-10-17 19:40:01 UTC
With audit enabled, the oops has not happened again, so it does indeed sound like a missing NULL pointer check could do it.

Comment 3 Josh Boyer 2013-01-02 17:17:29 UTC
This was backported to 3.6.3 with stable commit 724373bd489eb02e1999e2714fcc00658e081a9b


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