Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 189031

Summary: lsof crashes system
Product: Red Hat Enterprise Linux 4 Reporter: Eric Eisenhart <eric.eisenhart>
Component: kernelAssignee: Ingo Molnar <mingo>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: davej, eric.eisenhart, jbaron, mollo
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-18 17:24:30 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:
Bug Depends On:    
Bug Blocks: 170416    
Attachments:
Description Flags
screen capture from one crash
none
Another screen capture from a different system crashing from this bug none

Description Eric Eisenhart 2006-04-14 22:25:23 UTC
Description of problem:
Running lsof enough times results in a kernel crash.  Possible to do as a
non-root user.

Version-Release number of selected component (if applicable):
lsof-4.72-1.1
kernel-smp-2.6.9-34.EL

How reproducible:
Run this as any user:
while sleep 1; do for i in {1..100}; do /usr/sbin/lsof > /dev/null & done ; done
Give it several minutes.

(also possible to reproduce with much more reasonable uses of lsof, such as
something equivalent to "while sleep 60 ; do lsof ; done", but that takes
several days)

Steps to Reproduce:
1. Boot up RHEL4AS Update 3
2. run lsof a bunch of times, such as "while sleep 1; do for i in {1..100}; do
/usr/sbin/lsof > /dev/null & done ; done"
3. wait several minutes
  
Actual results:
kernel panic.  messages left on screen show the process as lsof and a call trace
showing seq_read, vfs_read, sys_read, syscall_call and schedule.

Expected results:
Not crashing.

Additional info:
Able to reproduce on several different systems with a 2.6.9-34 SMP kernel;
unable to reproduce on 2.6.9-22.0.1

Comment 1 Eric Eisenhart 2006-04-14 22:25:23 UTC
Created attachment 127763 [details]
screen capture from one crash

Comment 2 Eric Eisenhart 2006-04-14 22:28:13 UTC
Created attachment 127764 [details]
Another screen capture from a different system crashing from this bug

Comment 6 Jason Baron 2006-04-18 17:24:30 UTC

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