Bug 53386

Summary:	devfsd with recent rawhide kernels causes oops
Product:	[Retired] Red Hat Raw Hide	Reporter:	Alex Yacoub <ayacoub>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED DEFERRED	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-09-07 18:59:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Yacoub 2001-09-07 18:33:05 UTC

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 18:59:23 UTC

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 ;(