summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/ncr53c8xx.c
diff options
context:
space:
mode:
authorMartin Peschke <mpeschke@linux.vnet.ibm.com>2009-01-30 15:46:23 +0100
committerJames Bottomley <James.Bottomley@HansenPartnership.com>2009-02-10 11:15:17 -0500
commit76e3a19d0691bbfcc559ce77ab3004818fab8f22 (patch)
tree6013a3ec01ea3f269280740346b98875c35a5478 /drivers/scsi/ncr53c8xx.c
parentc2f9e49f9bbfa2e111ab1e1628b96b560bae7cec (diff)
downloadop-kernel-dev-76e3a19d0691bbfcc559ce77ab3004818fab8f22.zip
op-kernel-dev-76e3a19d0691bbfcc559ce77ab3004818fab8f22.tar.gz
[SCSI] sg: fix device number in blktrace data
Hi, we have run into an issue with blktrace being started for sg devices. Please apply. Thanks, Martin From: Martin Peschke <mpeschke@linux.vnet.ibm.com> The device number denoting a generic SCSI devices (sg) in a blktrace trace is broken; major and minor are always 0. It looks like sdp->device->sdev_gendev.devt is not initialized properly. The fix below uses other data to make up a valid device number, similar to the way an sg device number is generated for sysfs output. Reported-by: Stefan Raspl <raspl@linux.vnet.ibm.com> Signed-off-by: Martin Peschke <mpeschke@linux.vnet.ibm.com> Acked-by: Douglas Gilbert <dgilbert@interlog.com> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Diffstat (limited to 'drivers/scsi/ncr53c8xx.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud