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):
Steps to Reproduce:
1. Use the attached code to write data to an sg device
sg write succeeds
Created attachment 246961 [details]
source file that exhibits failure
Created attachment 246971 [details]
Additional header file required
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.
Thanks for the follow up. The code in attachment 1 [details] and 2 does not panic under
RHEL 5.1 ... Thanks!