Bug 364421 - Kernel panic when using sg driver to write
Kernel panic when using sg driver to write
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
low Severity high
: ---
: ---
Assigned To: Red Hat Kernel Manager
Martin Jenner
Depends On:
  Show dependency treegraph
Reported: 2007-11-02 14:55 EDT by Sean Bruno
Modified: 2008-04-21 09:40 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHEL 5.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-21 09:40:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
source file that exhibits failure (13.95 KB, text/plain)
2007-11-02 14:55 EDT, Sean Bruno
no flags Details
Additional header file required (617 bytes, application/octet-stream)
2007-11-02 14:56 EDT, Sean Bruno
no flags Details

  None (edit)
Description Sean Bruno 2007-11-02 14:55:59 EDT
Description of problem:
Using a custom program(attached) to write to an sg device causes a kernel panic.
 This behavior is seen with all CentOS 5 kernels. It is not seen in CentOS 4 or

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

How reproducible:

Steps to Reproduce:
1. Use the attached code to write data to an sg device
Actual results:
Kerne panic

Expected results:
sg write succeeds

Additional info:
Comment 1 Sean Bruno 2007-11-02 14:55:59 EDT
Created attachment 246961 [details]
source file that exhibits failure
Comment 2 Sean Bruno 2007-11-02 14:56:57 EDT
Created attachment 246971 [details]
Additional header file required
Comment 3 John Feeney 2008-04-16 17:23:15 EDT
Does this still fail in RHEL5.1? A fix was added to RHEL5.1 to prevent a 
panic within the sg driver when writing so I was wondering. I don't see a 
call trace of the panic so I can't compare it to the one found in the other
bugzilla. Hence my question.
Thanks for any feedback.
Comment 4 Sean Bruno 2008-04-18 23:37:16 EDT
Thanks for the follow up.  The code in attachment 1 [details] and 2 does not panic under
RHEL 5.1 ... Thanks!

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