Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 231128

Summary: megaraid_mbox driver, sysfs , proc_name should be fixed
Product: Red Hat Enterprise Linux 4 Reporter: Anatoly Pugachev <matorola>
Component: kernelAssignee: Chip Coldwell <coldwell>
Status: CLOSED NOTABUG QA Contact: Martin Jenner <mjenner>
Severity: low Docs Contact:
Priority: medium    
Version: 4.4CC: jbaron
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-14 15:32:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Anatoly Pugachev 2007-03-06 11:45:32 UTC
Description of problem:

on a system with megaraid driver (megaraid_mbox) , name from proc_name wrong

$ cat /sys/class/scsi_host/host0/proc_name 
megaraid

and should be megaraid_mbox

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

all 2.6.x kernels

How reproducible:

$ cat /sys/class/scsi_host/host0/proc_name 

Actual results:

megaraid

Expected results:

megaraid_mbox

Additional info:

please fix that problem, thanks.

Comment 1 Anatoly Pugachev 2007-03-06 11:47:51 UTC
$ grep -n proc_name *
megaraid_mbox.c:355:    .proc_name                      = "megaraid",
megaraid_sas.c:1046:    .proc_name = "megaraid_sas",
$ pwd
/home/mator/kernel/linux-2.6.20/drivers/scsi/megaraid


Comment 2 Chip Coldwell 2008-02-14 15:32:54 UTC
(In reply to comment #1)
> $ grep -n proc_name *
> megaraid_mbox.c:355:    .proc_name                      = "megaraid",

It is still thus in the upstream kernel.  We are not going to carry this diff;
make your request on the linux-scsi mailing list or directly to LSI.  Once it
goes in upstream, then we would be willing to take it in.

Chip