Bug 53386 – devfsd with recent rawhide kernels causes oops

Bug 53386 - devfsd with recent rawhide kernels causes oops

Summary:	devfsd with recent rawhide kernels causes oops

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Arjan van de Ven
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-09-07 14:33 EDT by Alex Yacoub
Modified:	2007-04-18 12:36 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-09-07 14:59:28 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Alex Yacoub 2001-09-07 14:33:05 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.7-2 i686; en-US; rv:0.9.1)
Gecko/20010622

Description of problem:
Compiling a new kernel from rawhide (I have tried 2.4.7-2 and 2.4.7-2.9)
and running with devfsd causes a kernel panic.  I currently run
2.4.0-0.43.4; I haven't tried anything in between.  I have tried many
different devfsd versions and sources.  I know you no longer include
devfsd, but causing a kernel panic is a big problem for something included
in the kernel...

I think this is a problem with pam, kernel, and devfsd.  The crash
sometimes goes away if I use the standard /etc/devfsd.conf file. 
Commenting out all lines (which approaches the way my file is set up) will
cause the crash, at least on my computer.

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


How reproducible:
Always

Steps to Reproduce:
1. Compile rawhide kernel
2. Install devfsd
3. Reboot.


Actual Results:  Crash occurs sometime during bootup or user login (not root).

Expected Results:  No crash...

Additional info:

Comment 1 Arjan van de Ven 2001-09-07 14:59:23 EDT

There's a good reason we don't enable devfs.... it is that is rather unstable
and has several user (eg non-root) causable oopses. The devfs maintainer knows
about these for several months now and it's not fixed yet ;(

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