Bug 243764 - consolekit daemon creates kernel oops
Summary: consolekit daemon creates kernel oops
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 7
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2007-06-11 19:05 UTC by Amin Astaneh
Modified: 2007-11-30 22:12 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2007-11-27 22:52:14 UTC

Attachments (Terms of Use)
The portion of /var/log/messages which contains the oops. (5.02 KB, text/plain)
2007-06-11 19:05 UTC, Amin Astaneh
no flags Details
patch attempting to fix problem (647 bytes, patch)
2007-06-11 23:26 UTC, Steve Grubb
no flags Details | Diff

Description Amin Astaneh 2007-06-11 19:05:18 UTC
Description of problem:
A kernel oops has been observed on an up-to-date f7 machine. No patterns as to
the cause have been found, therefore there is no way to determine
reproducibility at this time. The process that creates the oops condition is

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

How reproducible:
None. There is no pattern to how the error is produced.

Actual results:

Expected results:
No Oops.

Additional info:

Comment 1 Amin Astaneh 2007-06-11 19:05:18 UTC
Created attachment 156747 [details]
The portion of /var/log/messages which contains the oops.

Comment 2 Steve Grubb 2007-06-11 23:26:08 UTC
Created attachment 156768 [details]
patch attempting to fix problem

It appears that lookup_one_len() returns an error pointer sometimes. We should
make sure dir entry is valid before dereferencing. Not sure if the error should
be returned to sysfs_remove_group()'s caller.

Comment 3 Christopher Brown 2007-09-16 21:09:14 UTC

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.


I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while and the attached patch
appears to resolve the issue. Could you tell me if you are still having problems
with the latest kernel and if the patch was accepted upstream?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.


Comment 4 Chuck Ebbert 2007-11-27 22:52:14 UTC
Current kernel is now 2.6.23 and reporter has not responded.

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