Bug 442151 - use wait_queue_head_t to cause kernel crash on redhat3u9 on x86_64
Summary: use wait_queue_head_t to cause kernel crash on redhat3u9 on x86_64
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 3.9
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Don Howard
QA Contact: Martin Jenner
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-12 03:34 UTC by Gang He
Modified: 2008-07-02 18:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-02 18:23:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
bug source code (3.82 KB, application/x-zip-compressed)
2008-04-12 03:34 UTC, Gang He 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Gang He 2008-04-12 03:34:32 UTC 
Hi all,

I found a fatal bug in Redhat Enterprise Server 3 Update 9
<2.4.21-50.EL> on x86_64 when I used "wait_queue_head_t" data
structure, the same program works very well on i386, but porting it to
x86_64 will bring Linux kernel crash, who can help to take a look at
it, thanks.
all source code are as follows:
ghe.c - kernel module source file
mk.sh - command lines to compile all source files
read.c - read operation
write.c - write operation
rhel3u9-64bit.txt - oops output

Reproduce bug:
1) run  "./mk.sh" to compile all source files
2) run "insmod ghe.o" to insert kernel module to kernel
3) run "mknod /dev/ghe xxx" to create char device file
4) run "./devread" to read data from /dev/ghe
5) run "./devwrite" to write data to /dev/ghe, bug will take place.
Comment 1 Gang He 2008-04-12 03:34:32 UTC 
Created attachment 302190 [details]
bug source code
Comment 2 Gang He 2008-04-13 14:02:12 UTC 
Any engineer can take a look at it, thanks!
Comment 3 Eric Sandeen 2008-05-18 18:01:22 UTC 
From all appearances, this is most likely a bug in your driver, not in the
kernel, and hence probably not appropriate to file it as a bug against the RHEL3
kernel.
Note You need to log in before you can comment on or make changes to this bug.