2019-05-19 20:08:20 +08:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-only
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
* scsi.c Copyright (C) 1992 Drew Eckhardt
|
|
|
|
* Copyright (C) 1993, 1994, 1995, 1999 Eric Youngdale
|
|
|
|
* Copyright (C) 2002, 2003 Christoph Hellwig
|
|
|
|
*
|
|
|
|
* generic mid-level SCSI driver
|
|
|
|
* Initial versions: Drew Eckhardt
|
|
|
|
* Subsequent revisions: Eric Youngdale
|
|
|
|
*
|
|
|
|
* <drew@colorado.edu>
|
|
|
|
*
|
|
|
|
* Bug correction thanks go to :
|
|
|
|
* Rik Faith <faith@cs.unc.edu>
|
|
|
|
* Tommy Thorn <tthorn>
|
|
|
|
* Thomas Wuensche <tw@fgb1.fgb.mw.tu-muenchen.de>
|
|
|
|
*
|
|
|
|
* Modified by Eric Youngdale eric@andante.org or ericy@gnu.ai.mit.edu to
|
|
|
|
* add scatter-gather, multiple outstanding request, and other
|
|
|
|
* enhancements.
|
|
|
|
*
|
|
|
|
* Native multichannel, wide scsi, /proc/scsi and hot plugging
|
|
|
|
* support added by Michael Neuffer <mike@i-connect.net>
|
|
|
|
*
|
|
|
|
* Added request_module("scsi_hostadapter") for kerneld:
|
|
|
|
* (Put an "alias scsi_hostadapter your_hostadapter" in /etc/modprobe.conf)
|
|
|
|
* Bjorn Ekwall <bj0rn@blox.se>
|
|
|
|
* (changed to kmod)
|
|
|
|
*
|
|
|
|
* Major improvements to the timeout, abort, and reset processing,
|
|
|
|
* as well as performance modifications for large queue depths by
|
|
|
|
* Leonard N. Zubkoff <lnz@dandelion.com>
|
|
|
|
*
|
|
|
|
* Converted cli() code to spinlocks, Ingo Molnar
|
|
|
|
*
|
|
|
|
* Jiffies wrap fixes (host->resetting), 3 Dec 1998 Andrea Arcangeli
|
|
|
|
*
|
|
|
|
* out_of_space hacks, D. Gilbert (dpg) 990608
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/moduleparam.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/timer.h>
|
|
|
|
#include <linux/string.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/blkdev.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/completion.h>
|
|
|
|
#include <linux/unistd.h>
|
|
|
|
#include <linux/spinlock.h>
|
|
|
|
#include <linux/kmod.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/notifier.h>
|
|
|
|
#include <linux/cpu.h>
|
2006-01-11 20:16:10 +08:00
|
|
|
#include <linux/mutex.h>
|
2012-09-19 00:19:30 +08:00
|
|
|
#include <asm/unaligned.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
#include <scsi/scsi.h>
|
|
|
|
#include <scsi/scsi_cmnd.h>
|
|
|
|
#include <scsi/scsi_dbg.h>
|
|
|
|
#include <scsi/scsi_device.h>
|
Revert "scsi: revert "[SCSI] Get rid of scsi_cmnd->done""
This reverts commit ac40532ef0b8649e6f7f83859ea0de1c4ed08a19, which gets
us back the original cleanup of 6f5391c283d7fdcf24bf40786ea79061919d1e1d.
It turns out that the bug that was triggered by that commit was
apparently not actually triggered by that commit at all, and just the
testing conditions had changed enough to make it appear to be due to it.
The real problem seems to have been found by Peter Osterlund:
"pktcdvd sets it [block device size] when opening the /dev/pktcdvd
device, but when the drive is later opened as /dev/scd0, there is
nothing that sets it back. (Btw, 40944 is possible if the disk is a
CDRW that was formatted with "cdrwtool -m 10236".)
The problem is that pktcdvd opens the cd device in non-blocking mode
when pktsetup is run, and doesn't close it again until pktsetup -d is
run. The effect is that if you meanwhile open the cd device,
blkdev.c:do_open() doesn't call bd_set_size() because
bdev->bd_openers is non-zero."
In particular, to repeat the bug (regardless of whether commit
6f5391c283d7fdcf24bf40786ea79061919d1e1d is applied or not):
" 1. Start with an empty drive.
2. pktsetup 0 /dev/scd0
3. Insert a CD containing an isofs filesystem.
4. mount /dev/pktcdvd/0 /mnt/tmp
5. umount /mnt/tmp
6. Press the eject button.
7. Insert a DVD containing a non-writable filesystem.
8. mount /dev/scd0 /mnt/tmp
9. find /mnt/tmp -type f -print0 | xargs -0 sha1sum >/dev/null
10. If the DVD contains data beyond the physical size of a CD, you
get I/O errors in the terminal, and dmesg reports lots of
"attempt to access beyond end of device" errors."
which in turn is because the nested open after the media change won't
cause the size to be set properly (because the original open still holds
the block device, and we only do the bd_set_size() when we don't have
other people holding the device open).
The proper fix for that is probably to just do something like
bdev->bd_inode->i_size = (loff_t)get_capacity(disk)<<9;
in fs/block_dev.c:do_open() even for the cases where we're not the
original opener (but *not* call bd_set_size(), since that will also
change the block size of the device).
Cc: Peter Osterlund <petero2@telia.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox <matthew@wil.cx>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-01-07 02:17:12 +08:00
|
|
|
#include <scsi/scsi_driver.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
#include <scsi/scsi_eh.h>
|
|
|
|
#include <scsi/scsi_host.h>
|
|
|
|
#include <scsi/scsi_tcq.h>
|
|
|
|
|
|
|
|
#include "scsi_priv.h"
|
|
|
|
#include "scsi_logging.h"
|
|
|
|
|
2010-04-01 19:41:40 +08:00
|
|
|
#define CREATE_TRACE_POINTS
|
|
|
|
#include <trace/events/scsi.h>
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
* Definitions and constants.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Note - the initial logging level can be set here to log events at boot time.
|
|
|
|
* After the system is up, you may enable logging via the /proc interface.
|
|
|
|
*/
|
|
|
|
unsigned int scsi_logging_level;
|
|
|
|
#if defined(CONFIG_SCSI_LOGGING)
|
|
|
|
EXPORT_SYMBOL(scsi_logging_level);
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#ifdef CONFIG_SCSI_LOGGING
|
|
|
|
void scsi_log_send(struct scsi_cmnd *cmd)
|
|
|
|
{
|
|
|
|
unsigned int level;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If ML QUEUE log level is greater than or equal to:
|
|
|
|
*
|
|
|
|
* 1: nothing (match completion)
|
|
|
|
*
|
2014-10-24 20:27:01 +08:00
|
|
|
* 2: log opcode + command of all commands + cmd address
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
2014-10-24 20:27:01 +08:00
|
|
|
* 3: same as 2
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
2015-01-08 14:43:49 +08:00
|
|
|
* 4: same as 3
|
2005-04-17 06:20:36 +08:00
|
|
|
*/
|
|
|
|
if (unlikely(scsi_logging_level)) {
|
|
|
|
level = SCSI_LOG_LEVEL(SCSI_LOG_MLQUEUE_SHIFT,
|
|
|
|
SCSI_LOG_MLQUEUE_BITS);
|
|
|
|
if (level > 1) {
|
2014-10-24 20:27:01 +08:00
|
|
|
scmd_printk(KERN_INFO, cmd,
|
|
|
|
"Send: scmd 0x%p\n", cmd);
|
2005-04-17 06:20:36 +08:00
|
|
|
scsi_print_command(cmd);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void scsi_log_completion(struct scsi_cmnd *cmd, int disposition)
|
|
|
|
{
|
|
|
|
unsigned int level;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If ML COMPLETE log level is greater than or equal to:
|
|
|
|
*
|
|
|
|
* 1: log disposition, result, opcode + command, and conditionally
|
|
|
|
* sense data for failures or non SUCCESS dispositions.
|
|
|
|
*
|
|
|
|
* 2: same as 1 but for all command completions.
|
|
|
|
*
|
2014-10-24 20:27:01 +08:00
|
|
|
* 3: same as 2
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
|
|
|
* 4: same as 3 plus dump extra junk
|
|
|
|
*/
|
|
|
|
if (unlikely(scsi_logging_level)) {
|
|
|
|
level = SCSI_LOG_LEVEL(SCSI_LOG_MLCOMPLETE_SHIFT,
|
|
|
|
SCSI_LOG_MLCOMPLETE_BITS);
|
|
|
|
if (((level > 0) && (cmd->result || disposition != SUCCESS)) ||
|
|
|
|
(level > 1)) {
|
2015-01-08 14:43:47 +08:00
|
|
|
scsi_print_result(cmd, "Done", disposition);
|
2005-04-17 06:20:36 +08:00
|
|
|
scsi_print_command(cmd);
|
2021-04-27 16:30:14 +08:00
|
|
|
if (scsi_status_is_check_condition(cmd->result))
|
2014-10-24 20:26:45 +08:00
|
|
|
scsi_print_sense(cmd);
|
2007-02-28 11:40:27 +08:00
|
|
|
if (level > 3)
|
|
|
|
scmd_printk(KERN_INFO, cmd,
|
|
|
|
"scsi host busy %d failed %d\n",
|
2018-06-24 22:03:26 +08:00
|
|
|
scsi_host_busy(cmd->device->host),
|
2007-02-28 11:40:27 +08:00
|
|
|
cmd->device->host->host_failed);
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2007-11-04 02:30:39 +08:00
|
|
|
/**
|
|
|
|
* scsi_finish_command - cleanup and pass command back to upper layer
|
|
|
|
* @cmd: the command
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Description: Pass command off to upper layer for finishing of I/O
|
2005-04-17 06:20:36 +08:00
|
|
|
* request, waking processes that are waiting on results,
|
|
|
|
* etc.
|
|
|
|
*/
|
|
|
|
void scsi_finish_command(struct scsi_cmnd *cmd)
|
|
|
|
{
|
|
|
|
struct scsi_device *sdev = cmd->device;
|
[SCSI] Add helper code so transport classes/driver can control queueing (v3)
SCSI-ml manages the queueing limits for the device and host, but
does not do so at the target level. However something something similar
can come in userful when a driver is transitioning a transport object to
the the blocked state, becuase at that time we do not want to queue
io and we do not want the queuecommand to be called again.
The patch adds code similar to the exisiting SCSI_ML_*BUSY handlers.
You can now return SCSI_MLQUEUE_TARGET_BUSY when we hit
a transport level queueing issue like the hw cannot allocate some
resource at the iscsi session/connection level, or the target has temporarily
closed or shrunk the queueing window, or if we are transitioning
to the blocked state.
bnx2i, when they rework their firmware according to netdev
developers requests, will also need to be able to limit queueing at this
level. bnx2i will hook into libiscsi, but will allocate a scsi host per
netdevice/hba, so unlike pure software iscsi/iser which is allocating
a host per session, it cannot set the scsi_host->can_queue and return
SCSI_MLQUEUE_HOST_BUSY to reflect queueing limits on the transport.
The iscsi class/driver can also set a scsi_target->can_queue value which
reflects the max commands the driver/class can support. For iscsi this
reflects the number of commands we can support for each session due to
session/connection hw limits, driver limits, and to also reflect the
session/targets's queueing window.
Changes:
v1 - initial patch.
v2 - Fix scsi_run_queue handling of multiple blocked targets.
Previously we would break from the main loop if a device was added back on
the starved list. We now run over the list and check if any target is
blocked.
v3 - Rediff for scsi-misc.
Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
2008-08-18 04:24:38 +08:00
|
|
|
struct scsi_target *starget = scsi_target(sdev);
|
2005-04-17 06:20:36 +08:00
|
|
|
struct Scsi_Host *shost = sdev->host;
|
Revert "scsi: revert "[SCSI] Get rid of scsi_cmnd->done""
This reverts commit ac40532ef0b8649e6f7f83859ea0de1c4ed08a19, which gets
us back the original cleanup of 6f5391c283d7fdcf24bf40786ea79061919d1e1d.
It turns out that the bug that was triggered by that commit was
apparently not actually triggered by that commit at all, and just the
testing conditions had changed enough to make it appear to be due to it.
The real problem seems to have been found by Peter Osterlund:
"pktcdvd sets it [block device size] when opening the /dev/pktcdvd
device, but when the drive is later opened as /dev/scd0, there is
nothing that sets it back. (Btw, 40944 is possible if the disk is a
CDRW that was formatted with "cdrwtool -m 10236".)
The problem is that pktcdvd opens the cd device in non-blocking mode
when pktsetup is run, and doesn't close it again until pktsetup -d is
run. The effect is that if you meanwhile open the cd device,
blkdev.c:do_open() doesn't call bd_set_size() because
bdev->bd_openers is non-zero."
In particular, to repeat the bug (regardless of whether commit
6f5391c283d7fdcf24bf40786ea79061919d1e1d is applied or not):
" 1. Start with an empty drive.
2. pktsetup 0 /dev/scd0
3. Insert a CD containing an isofs filesystem.
4. mount /dev/pktcdvd/0 /mnt/tmp
5. umount /mnt/tmp
6. Press the eject button.
7. Insert a DVD containing a non-writable filesystem.
8. mount /dev/scd0 /mnt/tmp
9. find /mnt/tmp -type f -print0 | xargs -0 sha1sum >/dev/null
10. If the DVD contains data beyond the physical size of a CD, you
get I/O errors in the terminal, and dmesg reports lots of
"attempt to access beyond end of device" errors."
which in turn is because the nested open after the media change won't
cause the size to be set properly (because the original open still holds
the block device, and we only do the bd_set_size() when we don't have
other people holding the device open).
The proper fix for that is probably to just do something like
bdev->bd_inode->i_size = (loff_t)get_capacity(disk)<<9;
in fs/block_dev.c:do_open() even for the cases where we're not the
original opener (but *not* call bd_set_size(), since that will also
change the block size of the device).
Cc: Peter Osterlund <petero2@telia.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox <matthew@wil.cx>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-01-07 02:17:12 +08:00
|
|
|
struct scsi_driver *drv;
|
|
|
|
unsigned int good_bytes;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2019-10-25 14:58:55 +08:00
|
|
|
scsi_device_unbusy(sdev, cmd);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2014-01-23 19:07:41 +08:00
|
|
|
/*
|
|
|
|
* Clear the flags that say that the device/target/host is no longer
|
|
|
|
* capable of accepting new commands.
|
|
|
|
*/
|
|
|
|
if (atomic_read(&shost->host_blocked))
|
|
|
|
atomic_set(&shost->host_blocked, 0);
|
|
|
|
if (atomic_read(&starget->target_blocked))
|
|
|
|
atomic_set(&starget->target_blocked, 0);
|
|
|
|
if (atomic_read(&sdev->device_blocked))
|
|
|
|
atomic_set(&sdev->device_blocked, 0);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2005-10-25 06:04:06 +08:00
|
|
|
SCSI_LOG_MLCOMPLETE(4, sdev_printk(KERN_INFO, sdev,
|
|
|
|
"Notifying upper driver of completion "
|
|
|
|
"(result %x)\n", cmd->result));
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-04-11 18:56:52 +08:00
|
|
|
good_bytes = scsi_bufflen(cmd);
|
2021-08-10 07:03:05 +08:00
|
|
|
if (!blk_rq_is_passthrough(scsi_cmd_to_rq(cmd))) {
|
2008-03-09 08:24:17 +08:00
|
|
|
int old_good_bytes = good_bytes;
|
Revert "scsi: revert "[SCSI] Get rid of scsi_cmnd->done""
This reverts commit ac40532ef0b8649e6f7f83859ea0de1c4ed08a19, which gets
us back the original cleanup of 6f5391c283d7fdcf24bf40786ea79061919d1e1d.
It turns out that the bug that was triggered by that commit was
apparently not actually triggered by that commit at all, and just the
testing conditions had changed enough to make it appear to be due to it.
The real problem seems to have been found by Peter Osterlund:
"pktcdvd sets it [block device size] when opening the /dev/pktcdvd
device, but when the drive is later opened as /dev/scd0, there is
nothing that sets it back. (Btw, 40944 is possible if the disk is a
CDRW that was formatted with "cdrwtool -m 10236".)
The problem is that pktcdvd opens the cd device in non-blocking mode
when pktsetup is run, and doesn't close it again until pktsetup -d is
run. The effect is that if you meanwhile open the cd device,
blkdev.c:do_open() doesn't call bd_set_size() because
bdev->bd_openers is non-zero."
In particular, to repeat the bug (regardless of whether commit
6f5391c283d7fdcf24bf40786ea79061919d1e1d is applied or not):
" 1. Start with an empty drive.
2. pktsetup 0 /dev/scd0
3. Insert a CD containing an isofs filesystem.
4. mount /dev/pktcdvd/0 /mnt/tmp
5. umount /mnt/tmp
6. Press the eject button.
7. Insert a DVD containing a non-writable filesystem.
8. mount /dev/scd0 /mnt/tmp
9. find /mnt/tmp -type f -print0 | xargs -0 sha1sum >/dev/null
10. If the DVD contains data beyond the physical size of a CD, you
get I/O errors in the terminal, and dmesg reports lots of
"attempt to access beyond end of device" errors."
which in turn is because the nested open after the media change won't
cause the size to be set properly (because the original open still holds
the block device, and we only do the bd_set_size() when we don't have
other people holding the device open).
The proper fix for that is probably to just do something like
bdev->bd_inode->i_size = (loff_t)get_capacity(disk)<<9;
in fs/block_dev.c:do_open() even for the cases where we're not the
original opener (but *not* call bd_set_size(), since that will also
change the block size of the device).
Cc: Peter Osterlund <petero2@telia.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox <matthew@wil.cx>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-01-07 02:17:12 +08:00
|
|
|
drv = scsi_cmd_to_driver(cmd);
|
|
|
|
if (drv->done)
|
|
|
|
good_bytes = drv->done(cmd);
|
2008-03-09 08:24:17 +08:00
|
|
|
/*
|
|
|
|
* USB may not give sense identifying bad sector and
|
|
|
|
* simply return a residue instead, so subtract off the
|
|
|
|
* residue if drv->done() error processing indicates no
|
|
|
|
* change to the completion length.
|
|
|
|
*/
|
|
|
|
if (good_bytes == old_good_bytes)
|
|
|
|
good_bytes -= scsi_get_resid(cmd);
|
Revert "scsi: revert "[SCSI] Get rid of scsi_cmnd->done""
This reverts commit ac40532ef0b8649e6f7f83859ea0de1c4ed08a19, which gets
us back the original cleanup of 6f5391c283d7fdcf24bf40786ea79061919d1e1d.
It turns out that the bug that was triggered by that commit was
apparently not actually triggered by that commit at all, and just the
testing conditions had changed enough to make it appear to be due to it.
The real problem seems to have been found by Peter Osterlund:
"pktcdvd sets it [block device size] when opening the /dev/pktcdvd
device, but when the drive is later opened as /dev/scd0, there is
nothing that sets it back. (Btw, 40944 is possible if the disk is a
CDRW that was formatted with "cdrwtool -m 10236".)
The problem is that pktcdvd opens the cd device in non-blocking mode
when pktsetup is run, and doesn't close it again until pktsetup -d is
run. The effect is that if you meanwhile open the cd device,
blkdev.c:do_open() doesn't call bd_set_size() because
bdev->bd_openers is non-zero."
In particular, to repeat the bug (regardless of whether commit
6f5391c283d7fdcf24bf40786ea79061919d1e1d is applied or not):
" 1. Start with an empty drive.
2. pktsetup 0 /dev/scd0
3. Insert a CD containing an isofs filesystem.
4. mount /dev/pktcdvd/0 /mnt/tmp
5. umount /mnt/tmp
6. Press the eject button.
7. Insert a DVD containing a non-writable filesystem.
8. mount /dev/scd0 /mnt/tmp
9. find /mnt/tmp -type f -print0 | xargs -0 sha1sum >/dev/null
10. If the DVD contains data beyond the physical size of a CD, you
get I/O errors in the terminal, and dmesg reports lots of
"attempt to access beyond end of device" errors."
which in turn is because the nested open after the media change won't
cause the size to be set properly (because the original open still holds
the block device, and we only do the bd_set_size() when we don't have
other people holding the device open).
The proper fix for that is probably to just do something like
bdev->bd_inode->i_size = (loff_t)get_capacity(disk)<<9;
in fs/block_dev.c:do_open() even for the cases where we're not the
original opener (but *not* call bd_set_size(), since that will also
change the block size of the device).
Cc: Peter Osterlund <petero2@telia.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox <matthew@wil.cx>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-01-07 02:17:12 +08:00
|
|
|
}
|
|
|
|
scsi_io_completion(cmd, good_bytes);
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
|
2021-01-22 10:33:16 +08:00
|
|
|
|
|
|
|
/*
|
2022-04-14 18:36:01 +08:00
|
|
|
* 4096 is big enough for saturating fast SCSI LUNs.
|
2021-01-22 10:33:16 +08:00
|
|
|
*/
|
2021-01-22 10:33:17 +08:00
|
|
|
int scsi_device_max_queue_depth(struct scsi_device *sdev)
|
2021-01-22 10:33:16 +08:00
|
|
|
{
|
2022-04-14 18:36:01 +08:00
|
|
|
return min_t(int, sdev->host->can_queue, 4096);
|
2021-01-22 10:33:16 +08:00
|
|
|
}
|
|
|
|
|
2007-11-04 02:30:39 +08:00
|
|
|
/**
|
2014-11-13 22:08:42 +08:00
|
|
|
* scsi_change_queue_depth - change a device's queue depth
|
2007-11-04 02:30:39 +08:00
|
|
|
* @sdev: SCSI Device in question
|
2014-11-13 22:08:42 +08:00
|
|
|
* @depth: number of commands allowed to be queued to the driver
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
2014-11-13 22:08:42 +08:00
|
|
|
* Sets the device queue depth and returns the new value.
|
2005-04-17 06:20:36 +08:00
|
|
|
*/
|
2014-11-13 22:08:42 +08:00
|
|
|
int scsi_change_queue_depth(struct scsi_device *sdev, int depth)
|
2005-04-17 06:20:36 +08:00
|
|
|
{
|
2021-01-22 10:33:16 +08:00
|
|
|
depth = min_t(int, depth, scsi_device_max_queue_depth(sdev));
|
|
|
|
|
2015-10-08 16:28:04 +08:00
|
|
|
if (depth > 0) {
|
|
|
|
sdev->queue_depth = depth;
|
|
|
|
wmb();
|
2008-07-12 08:50:32 +08:00
|
|
|
}
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2016-03-31 00:21:08 +08:00
|
|
|
if (sdev->request_queue)
|
|
|
|
blk_set_queue_depth(sdev->request_queue, depth);
|
|
|
|
|
2021-01-22 10:33:17 +08:00
|
|
|
sbitmap_resize(&sdev->budget_map, sdev->queue_depth);
|
|
|
|
|
2014-11-13 22:08:42 +08:00
|
|
|
return sdev->queue_depth;
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
2014-11-13 22:08:42 +08:00
|
|
|
EXPORT_SYMBOL(scsi_change_queue_depth);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-11-04 02:30:39 +08:00
|
|
|
/**
|
|
|
|
* scsi_track_queue_full - track QUEUE_FULL events to adjust queue depth
|
|
|
|
* @sdev: SCSI Device in question
|
|
|
|
* @depth: Current number of outstanding SCSI commands on this device,
|
|
|
|
* not counting the one returned as QUEUE_FULL.
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Description: This function will track successive QUEUE_FULL events on a
|
2005-04-17 06:20:36 +08:00
|
|
|
* specific SCSI device to determine if and when there is a
|
|
|
|
* need to adjust the queue depth on the device.
|
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Returns: 0 - No change needed, >0 - Adjust queue depth to this new depth,
|
2005-04-17 06:20:36 +08:00
|
|
|
* -1 - Drop back to untagged operation using host->cmd_per_lun
|
|
|
|
* as the untagged command depth
|
|
|
|
*
|
|
|
|
* Lock Status: None held on entry
|
|
|
|
*
|
|
|
|
* Notes: Low level drivers may call this at any time and we will do
|
|
|
|
* "The Right Thing." We are interrupt context safe.
|
|
|
|
*/
|
|
|
|
int scsi_track_queue_full(struct scsi_device *sdev, int depth)
|
|
|
|
{
|
2009-10-23 06:46:33 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Don't let QUEUE_FULLs on the same
|
|
|
|
* jiffies count, they could all be from
|
|
|
|
* same event.
|
|
|
|
*/
|
|
|
|
if ((jiffies >> 4) == (sdev->last_queue_full_time >> 4))
|
2005-04-17 06:20:36 +08:00
|
|
|
return 0;
|
|
|
|
|
2009-10-23 06:46:33 +08:00
|
|
|
sdev->last_queue_full_time = jiffies;
|
2005-04-17 06:20:36 +08:00
|
|
|
if (sdev->last_queue_full_depth != depth) {
|
|
|
|
sdev->last_queue_full_count = 1;
|
|
|
|
sdev->last_queue_full_depth = depth;
|
|
|
|
} else {
|
|
|
|
sdev->last_queue_full_count++;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (sdev->last_queue_full_count <= 10)
|
|
|
|
return 0;
|
2014-10-30 18:54:58 +08:00
|
|
|
|
2014-11-13 22:08:42 +08:00
|
|
|
return scsi_change_queue_depth(sdev, depth);
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(scsi_track_queue_full);
|
|
|
|
|
2009-01-01 02:12:46 +08:00
|
|
|
/**
|
|
|
|
* scsi_vpd_inquiry - Request a device provide us with a VPD page
|
|
|
|
* @sdev: The device to ask
|
|
|
|
* @buffer: Where to put the result
|
|
|
|
* @page: Which Vital Product Data to return
|
|
|
|
* @len: The length of the buffer
|
|
|
|
*
|
|
|
|
* This is an internal helper function. You probably want to use
|
|
|
|
* scsi_get_vpd_page instead.
|
|
|
|
*
|
2014-03-15 16:51:48 +08:00
|
|
|
* Returns size of the vpd page on success or a negative error number.
|
2009-01-01 02:12:46 +08:00
|
|
|
*/
|
|
|
|
static int scsi_vpd_inquiry(struct scsi_device *sdev, unsigned char *buffer,
|
|
|
|
u8 page, unsigned len)
|
|
|
|
{
|
|
|
|
int result;
|
|
|
|
unsigned char cmd[16];
|
|
|
|
|
2014-03-15 16:51:48 +08:00
|
|
|
if (len < 4)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2009-01-01 02:12:46 +08:00
|
|
|
cmd[0] = INQUIRY;
|
|
|
|
cmd[1] = 1; /* EVPD */
|
|
|
|
cmd[2] = page;
|
|
|
|
cmd[3] = len >> 8;
|
|
|
|
cmd[4] = len & 0xff;
|
|
|
|
cmd[5] = 0; /* Control byte */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* I'm not convinced we need to try quite this hard to get VPD, but
|
|
|
|
* all the existing users tried this hard.
|
|
|
|
*/
|
2022-12-30 03:01:45 +08:00
|
|
|
result = scsi_execute_cmd(sdev, cmd, REQ_OP_DRV_IN, buffer, len,
|
|
|
|
30 * HZ, 3, NULL);
|
2009-01-01 02:12:46 +08:00
|
|
|
if (result)
|
2014-03-15 16:51:48 +08:00
|
|
|
return -EIO;
|
2009-01-01 02:12:46 +08:00
|
|
|
|
2023-03-22 10:22:11 +08:00
|
|
|
/*
|
|
|
|
* Sanity check that we got the page back that we asked for and that
|
|
|
|
* the page size is not 0.
|
|
|
|
*/
|
2009-01-01 02:12:46 +08:00
|
|
|
if (buffer[1] != page)
|
|
|
|
return -EIO;
|
|
|
|
|
2023-03-22 10:22:11 +08:00
|
|
|
result = get_unaligned_be16(&buffer[2]);
|
|
|
|
if (!result)
|
|
|
|
return -EIO;
|
|
|
|
|
|
|
|
return result + 4;
|
2009-01-01 02:12:46 +08:00
|
|
|
}
|
|
|
|
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
static int scsi_get_vpd_size(struct scsi_device *sdev, u8 page)
|
|
|
|
{
|
|
|
|
unsigned char vpd_header[SCSI_VPD_HEADER_SIZE] __aligned(4);
|
|
|
|
int result;
|
|
|
|
|
2022-09-29 02:13:50 +08:00
|
|
|
if (sdev->no_vpd_size)
|
|
|
|
return SCSI_DEFAULT_VPD_LEN;
|
|
|
|
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
/*
|
|
|
|
* Fetch the VPD page header to find out how big the page
|
|
|
|
* is. This is done to prevent problems on legacy devices
|
|
|
|
* which can not handle allocation lengths as large as
|
|
|
|
* potentially requested by the caller.
|
|
|
|
*/
|
|
|
|
result = scsi_vpd_inquiry(sdev, vpd_header, page, sizeof(vpd_header));
|
|
|
|
if (result < 0)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (result < SCSI_VPD_HEADER_SIZE) {
|
|
|
|
dev_warn_once(&sdev->sdev_gendev,
|
|
|
|
"%s: short VPD page 0x%02x length: %d bytes\n",
|
|
|
|
__func__, page, result);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
|
2009-01-01 02:12:46 +08:00
|
|
|
/**
|
|
|
|
* scsi_get_vpd_page - Get Vital Product Data from a SCSI device
|
|
|
|
* @sdev: The device to ask
|
|
|
|
* @page: Which Vital Product Data to return
|
2010-03-01 09:32:45 +08:00
|
|
|
* @buf: where to store the VPD
|
|
|
|
* @buf_len: number of bytes in the VPD buffer area
|
2009-01-01 02:12:46 +08:00
|
|
|
*
|
|
|
|
* SCSI devices may optionally supply Vital Product Data. Each 'page'
|
|
|
|
* of VPD is defined in the appropriate SCSI document (eg SPC, SBC).
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
* If the device supports this VPD page, this routine fills @buf
|
|
|
|
* with the data from that page and return 0. If the VPD page is not
|
|
|
|
* supported or its content cannot be retrieved, -EINVAL is returned.
|
2009-01-01 02:12:46 +08:00
|
|
|
*/
|
2009-11-04 02:33:07 +08:00
|
|
|
int scsi_get_vpd_page(struct scsi_device *sdev, u8 page, unsigned char *buf,
|
|
|
|
int buf_len)
|
2009-01-01 02:12:46 +08:00
|
|
|
{
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
int result, vpd_len;
|
2009-01-01 02:12:46 +08:00
|
|
|
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
if (!scsi_device_supports_vpd(sdev))
|
|
|
|
return -EINVAL;
|
2009-01-01 02:12:46 +08:00
|
|
|
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
vpd_len = scsi_get_vpd_size(sdev, page);
|
|
|
|
if (vpd_len <= 0)
|
|
|
|
return -EINVAL;
|
2009-11-04 02:33:07 +08:00
|
|
|
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
vpd_len = min(vpd_len, buf_len);
|
2009-01-01 02:12:46 +08:00
|
|
|
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
/*
|
|
|
|
* Fetch the actual page. Since the appropriate size was reported
|
|
|
|
* by the device it is now safe to ask for something bigger.
|
|
|
|
*/
|
|
|
|
memset(buf, 0, buf_len);
|
|
|
|
result = scsi_vpd_inquiry(sdev, buf, page, vpd_len);
|
2014-03-15 16:51:48 +08:00
|
|
|
if (result < 0)
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
return -EINVAL;
|
|
|
|
else if (result > vpd_len)
|
|
|
|
dev_warn_once(&sdev->sdev_gendev,
|
|
|
|
"%s: VPD page 0x%02x result %d > %d bytes\n",
|
|
|
|
__func__, page, result, vpd_len);
|
2009-01-01 02:12:46 +08:00
|
|
|
|
2009-11-04 02:33:07 +08:00
|
|
|
return 0;
|
2009-01-01 02:12:46 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(scsi_get_vpd_page);
|
|
|
|
|
2017-08-29 23:50:12 +08:00
|
|
|
/**
|
|
|
|
* scsi_get_vpd_buf - Get Vital Product Data from a SCSI device
|
|
|
|
* @sdev: The device to ask
|
|
|
|
* @page: Which Vital Product Data to return
|
|
|
|
*
|
|
|
|
* Returns %NULL upon failure.
|
|
|
|
*/
|
2017-08-29 23:50:13 +08:00
|
|
|
static struct scsi_vpd *scsi_get_vpd_buf(struct scsi_device *sdev, u8 page)
|
2017-08-29 23:50:12 +08:00
|
|
|
{
|
2017-08-29 23:50:13 +08:00
|
|
|
struct scsi_vpd *vpd_buf;
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
int vpd_len, result;
|
|
|
|
|
|
|
|
vpd_len = scsi_get_vpd_size(sdev, page);
|
|
|
|
if (vpd_len <= 0)
|
|
|
|
return NULL;
|
2017-08-29 23:50:12 +08:00
|
|
|
|
|
|
|
retry_pg:
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
/*
|
|
|
|
* Fetch the actual page. Since the appropriate size was reported
|
|
|
|
* by the device it is now safe to ask for something bigger.
|
|
|
|
*/
|
2017-08-29 23:50:13 +08:00
|
|
|
vpd_buf = kmalloc(sizeof(*vpd_buf) + vpd_len, GFP_KERNEL);
|
2017-08-29 23:50:12 +08:00
|
|
|
if (!vpd_buf)
|
|
|
|
return NULL;
|
|
|
|
|
2017-08-29 23:50:13 +08:00
|
|
|
result = scsi_vpd_inquiry(sdev, vpd_buf->data, page, vpd_len);
|
2017-08-29 23:50:12 +08:00
|
|
|
if (result < 0) {
|
|
|
|
kfree(vpd_buf);
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
if (result > vpd_len) {
|
scsi: core: Query VPD size before getting full page
We currently default to 255 bytes when fetching VPD pages during discovery.
However, we have had a few devices that are known to wedge if the requested
buffer exceeds a certain size. See commit af73623f5f10 ("[SCSI] sd: Reduce
buffer size for vpd request") which works around one example of this
problem in the SCSI disk driver.
With commit d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages
0h and 89h") we now risk triggering the same issue in the generic midlayer
code.
The problem with the ATA VPD page in particular is that the SCSI portion of
the page is trailed by 512 bytes of verbatim ATA Identify Device
information. However, not all controllers actually provide the additional
512 bytes and will lock up if one asks for more than the 64 bytes
containing the SCSI protocol fields.
Instead of picking a new, somewhat arbitrary, number of bytes for the VPD
buffer size, start fetching the 4-byte header for each page. The header
contains the size of the page as far as the device is concerned. We can use
the reported size to specify the correct allocation length when
subsequently fetching the full page.
The header validation is done by a new helper function scsi_get_vpd_size()
and both scsi_get_vpd_page() and scsi_get_vpd_buf() now rely on this to
query the page size.
In addition, scsi_get_vpd_page() is simplified to mirror the logic in
scsi_get_vpd_page(). This involves removing the Supported VPD Pages lookup
prior to attempting to query a page. There does not appear any evidence,
even in the oldest SCSI specs, that this step is required. We already rely
on scsi_get_vpd_page() throughout the stack and this function never
consulted the Supported VPD Pages. Since this has not caused any problems
it should be safe to remove the precondition from scsi_get_vpd_page().
Instrumented runs also revealed that the Supported VPD Pages lookup had
little effect since the device page index often was larger than the
supplied buffer size. As a result, inquiries frequently bypassed the index
check and went through the "If we ran off the end of the buffer, give us
the benefit of the doubt" code path which assumed the page was present
despite not being listed. The revised code takes both the page size
reported by the device as well as the size of the buffer provided by the
scsi_get_vpd_page() caller into account.
Link: https://lore.kernel.org/r/20220302053559.32147-3-martin.petersen@oracle.com
Fixes: d188b0675b21 ("scsi: core: Add sysfs attributes for VPD pages 0h and 89h")
Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2022-03-02 13:35:47 +08:00
|
|
|
dev_warn_once(&sdev->sdev_gendev,
|
|
|
|
"%s: VPD page 0x%02x result %d > %d bytes\n",
|
|
|
|
__func__, page, result, vpd_len);
|
2017-08-29 23:50:12 +08:00
|
|
|
vpd_len = result;
|
|
|
|
kfree(vpd_buf);
|
|
|
|
goto retry_pg;
|
|
|
|
}
|
|
|
|
|
2017-08-29 23:50:13 +08:00
|
|
|
vpd_buf->len = result;
|
2017-08-29 23:50:12 +08:00
|
|
|
|
|
|
|
return vpd_buf;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void scsi_update_vpd_page(struct scsi_device *sdev, u8 page,
|
2017-08-29 23:50:13 +08:00
|
|
|
struct scsi_vpd __rcu **sdev_vpd_buf)
|
2017-08-29 23:50:12 +08:00
|
|
|
{
|
2017-08-29 23:50:13 +08:00
|
|
|
struct scsi_vpd *vpd_buf;
|
2017-08-29 23:50:12 +08:00
|
|
|
|
2017-08-29 23:50:13 +08:00
|
|
|
vpd_buf = scsi_get_vpd_buf(sdev, page);
|
2017-08-29 23:50:12 +08:00
|
|
|
if (!vpd_buf)
|
|
|
|
return;
|
|
|
|
|
|
|
|
mutex_lock(&sdev->inquiry_mutex);
|
2019-09-24 06:26:28 +08:00
|
|
|
vpd_buf = rcu_replace_pointer(*sdev_vpd_buf, vpd_buf,
|
|
|
|
lockdep_is_held(&sdev->inquiry_mutex));
|
2017-08-29 23:50:12 +08:00
|
|
|
mutex_unlock(&sdev->inquiry_mutex);
|
|
|
|
|
2017-08-29 23:50:13 +08:00
|
|
|
if (vpd_buf)
|
|
|
|
kfree_rcu(vpd_buf, rcu);
|
2017-08-29 23:50:12 +08:00
|
|
|
}
|
|
|
|
|
2014-03-15 16:51:49 +08:00
|
|
|
/**
|
|
|
|
* scsi_attach_vpd - Attach Vital Product Data to a SCSI device structure
|
|
|
|
* @sdev: The device to ask
|
|
|
|
*
|
|
|
|
* Attach the 'Device Identification' VPD page (0x83) and the
|
|
|
|
* 'Unit Serial Number' VPD page (0x80) to a SCSI device
|
|
|
|
* structure. This information can be used to identify the device
|
|
|
|
* uniquely.
|
|
|
|
*/
|
|
|
|
void scsi_attach_vpd(struct scsi_device *sdev)
|
|
|
|
{
|
2017-08-29 23:50:13 +08:00
|
|
|
int i;
|
|
|
|
struct scsi_vpd *vpd_buf;
|
2014-03-15 16:51:49 +08:00
|
|
|
|
2016-04-01 14:57:36 +08:00
|
|
|
if (!scsi_device_supports_vpd(sdev))
|
2014-03-15 16:51:49 +08:00
|
|
|
return;
|
2016-04-01 14:57:36 +08:00
|
|
|
|
2014-03-15 16:51:49 +08:00
|
|
|
/* Ask for all the pages supported by this device */
|
2017-08-29 23:50:13 +08:00
|
|
|
vpd_buf = scsi_get_vpd_buf(sdev, 0);
|
2017-08-29 23:50:12 +08:00
|
|
|
if (!vpd_buf)
|
2014-03-15 16:51:49 +08:00
|
|
|
return;
|
|
|
|
|
2017-08-29 23:50:13 +08:00
|
|
|
for (i = 4; i < vpd_buf->len; i++) {
|
2019-09-27 00:22:17 +08:00
|
|
|
if (vpd_buf->data[i] == 0x0)
|
|
|
|
scsi_update_vpd_page(sdev, 0x0, &sdev->vpd_pg0);
|
2017-08-29 23:50:13 +08:00
|
|
|
if (vpd_buf->data[i] == 0x80)
|
|
|
|
scsi_update_vpd_page(sdev, 0x80, &sdev->vpd_pg80);
|
|
|
|
if (vpd_buf->data[i] == 0x83)
|
|
|
|
scsi_update_vpd_page(sdev, 0x83, &sdev->vpd_pg83);
|
2019-09-27 00:22:17 +08:00
|
|
|
if (vpd_buf->data[i] == 0x89)
|
|
|
|
scsi_update_vpd_page(sdev, 0x89, &sdev->vpd_pg89);
|
2022-03-02 13:35:50 +08:00
|
|
|
if (vpd_buf->data[i] == 0xb0)
|
|
|
|
scsi_update_vpd_page(sdev, 0xb0, &sdev->vpd_pgb0);
|
|
|
|
if (vpd_buf->data[i] == 0xb1)
|
|
|
|
scsi_update_vpd_page(sdev, 0xb1, &sdev->vpd_pgb1);
|
|
|
|
if (vpd_buf->data[i] == 0xb2)
|
|
|
|
scsi_update_vpd_page(sdev, 0xb2, &sdev->vpd_pgb2);
|
2014-03-15 16:51:49 +08:00
|
|
|
}
|
|
|
|
kfree(vpd_buf);
|
|
|
|
}
|
|
|
|
|
2012-09-19 00:19:30 +08:00
|
|
|
/**
|
2023-05-11 09:13:40 +08:00
|
|
|
* scsi_report_opcode - Find out if a given command is supported
|
2012-09-19 00:19:30 +08:00
|
|
|
* @sdev: scsi device to query
|
|
|
|
* @buffer: scratch buffer (must be at least 20 bytes long)
|
|
|
|
* @len: length of buffer
|
2023-05-11 09:13:40 +08:00
|
|
|
* @opcode: opcode for the command to look up
|
|
|
|
* @sa: service action for the command to look up
|
2012-09-19 00:19:30 +08:00
|
|
|
*
|
2023-05-11 09:13:40 +08:00
|
|
|
* Uses the REPORT SUPPORTED OPERATION CODES to check support for the
|
|
|
|
* command identified with @opcode and @sa. If the command does not
|
|
|
|
* have a service action, @sa must be 0. Returns -EINVAL if RSOC fails,
|
|
|
|
* 0 if the command is not supported and 1 if the device claims to
|
|
|
|
* support the command.
|
2012-09-19 00:19:30 +08:00
|
|
|
*/
|
|
|
|
int scsi_report_opcode(struct scsi_device *sdev, unsigned char *buffer,
|
2023-05-11 09:13:40 +08:00
|
|
|
unsigned int len, unsigned char opcode,
|
|
|
|
unsigned short sa)
|
2012-09-19 00:19:30 +08:00
|
|
|
{
|
|
|
|
unsigned char cmd[16];
|
|
|
|
struct scsi_sense_hdr sshdr;
|
2022-03-02 13:35:49 +08:00
|
|
|
int result, request_len;
|
2022-12-30 03:01:45 +08:00
|
|
|
const struct scsi_exec_args exec_args = {
|
|
|
|
.sshdr = &sshdr,
|
|
|
|
};
|
2012-09-19 00:19:30 +08:00
|
|
|
|
|
|
|
if (sdev->no_report_opcodes || sdev->scsi_level < SCSI_SPC_3)
|
2013-06-07 10:15:55 +08:00
|
|
|
return -EINVAL;
|
2012-09-19 00:19:30 +08:00
|
|
|
|
2022-03-02 13:35:49 +08:00
|
|
|
/* RSOC header + size of command we are asking about */
|
|
|
|
request_len = 4 + COMMAND_SIZE(opcode);
|
|
|
|
if (request_len > len) {
|
|
|
|
dev_warn_once(&sdev->sdev_gendev,
|
|
|
|
"%s: len %u bytes, opcode 0x%02x needs %u\n",
|
|
|
|
__func__, len, opcode, request_len);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2012-09-19 00:19:30 +08:00
|
|
|
memset(cmd, 0, 16);
|
|
|
|
cmd[0] = MAINTENANCE_IN;
|
|
|
|
cmd[1] = MI_REPORT_SUPPORTED_OPERATION_CODES;
|
2023-05-11 09:13:40 +08:00
|
|
|
if (!sa) {
|
|
|
|
cmd[2] = 1; /* One command format */
|
|
|
|
cmd[3] = opcode;
|
|
|
|
} else {
|
|
|
|
cmd[2] = 3; /* One command format with service action */
|
|
|
|
cmd[3] = opcode;
|
|
|
|
put_unaligned_be16(sa, &cmd[4]);
|
|
|
|
}
|
2022-03-02 13:35:49 +08:00
|
|
|
put_unaligned_be32(request_len, &cmd[6]);
|
2012-09-19 00:19:30 +08:00
|
|
|
memset(buffer, 0, len);
|
|
|
|
|
2022-12-30 03:01:45 +08:00
|
|
|
result = scsi_execute_cmd(sdev, cmd, REQ_OP_DRV_IN, buffer,
|
|
|
|
request_len, 30 * HZ, 3, &exec_args);
|
2021-04-27 16:30:12 +08:00
|
|
|
if (result < 0)
|
|
|
|
return result;
|
2012-09-19 00:19:30 +08:00
|
|
|
if (result && scsi_sense_valid(&sshdr) &&
|
|
|
|
sshdr.sense_key == ILLEGAL_REQUEST &&
|
|
|
|
(sshdr.asc == 0x20 || sshdr.asc == 0x24) && sshdr.ascq == 0x00)
|
2013-06-07 10:15:55 +08:00
|
|
|
return -EINVAL;
|
2012-09-19 00:19:30 +08:00
|
|
|
|
|
|
|
if ((buffer[1] & 3) == 3) /* Command supported */
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(scsi_report_opcode);
|
|
|
|
|
2023-05-11 09:13:41 +08:00
|
|
|
#define SCSI_CDL_CHECK_BUF_LEN 64
|
|
|
|
|
|
|
|
static bool scsi_cdl_check_cmd(struct scsi_device *sdev, u8 opcode, u16 sa,
|
|
|
|
unsigned char *buf)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
u8 cdlp;
|
|
|
|
|
|
|
|
/* Check operation code */
|
|
|
|
ret = scsi_report_opcode(sdev, buf, SCSI_CDL_CHECK_BUF_LEN, opcode, sa);
|
|
|
|
if (ret <= 0)
|
|
|
|
return false;
|
|
|
|
|
|
|
|
if ((buf[1] & 0x03) != 0x03)
|
|
|
|
return false;
|
|
|
|
|
2023-06-23 15:30:57 +08:00
|
|
|
/*
|
|
|
|
* See SPC-6, One_command parameter data format for
|
|
|
|
* REPORT SUPPORTED OPERATION CODES. We have the following cases
|
|
|
|
* depending on rwcdlp (buf[0] & 0x01) value:
|
|
|
|
* - rwcdlp == 0: then cdlp indicates support for the A mode page when
|
|
|
|
* it is equal to 1 and for the B mode page when it is
|
|
|
|
* equal to 2.
|
|
|
|
* - rwcdlp == 1: then cdlp indicates support for the T2A mode page
|
|
|
|
* when it is equal to 1 and for the T2B mode page when
|
|
|
|
* it is equal to 2.
|
|
|
|
* Overall, to detect support for command duration limits, we only need
|
|
|
|
* to check that cdlp is 1 or 2.
|
|
|
|
*/
|
2023-05-11 09:13:41 +08:00
|
|
|
cdlp = (buf[1] & 0x18) >> 3;
|
|
|
|
|
2023-06-23 15:30:57 +08:00
|
|
|
return cdlp == 0x01 || cdlp == 0x02;
|
2023-05-11 09:13:41 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* scsi_cdl_check - Check if a SCSI device supports Command Duration Limits
|
|
|
|
* @sdev: The device to check
|
|
|
|
*/
|
|
|
|
void scsi_cdl_check(struct scsi_device *sdev)
|
|
|
|
{
|
|
|
|
bool cdl_supported;
|
|
|
|
unsigned char *buf;
|
|
|
|
|
|
|
|
buf = kmalloc(SCSI_CDL_CHECK_BUF_LEN, GFP_KERNEL);
|
|
|
|
if (!buf) {
|
|
|
|
sdev->cdl_supported = 0;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Check support for READ_16, WRITE_16, READ_32 and WRITE_32 commands */
|
|
|
|
cdl_supported =
|
|
|
|
scsi_cdl_check_cmd(sdev, READ_16, 0, buf) ||
|
|
|
|
scsi_cdl_check_cmd(sdev, WRITE_16, 0, buf) ||
|
|
|
|
scsi_cdl_check_cmd(sdev, VARIABLE_LENGTH_CMD, READ_32, buf) ||
|
|
|
|
scsi_cdl_check_cmd(sdev, VARIABLE_LENGTH_CMD, WRITE_32, buf);
|
|
|
|
if (cdl_supported) {
|
|
|
|
/*
|
|
|
|
* We have CDL support: force the use of READ16/WRITE16.
|
|
|
|
* READ32 and WRITE32 will be used for devices that support
|
|
|
|
* the T10_PI_TYPE2_PROTECTION protection type.
|
|
|
|
*/
|
|
|
|
sdev->use_16_for_rw = 1;
|
|
|
|
sdev->use_10_for_rw = 0;
|
|
|
|
|
|
|
|
sdev->cdl_supported = 1;
|
|
|
|
} else {
|
|
|
|
sdev->cdl_supported = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
kfree(buf);
|
|
|
|
}
|
|
|
|
|
2023-05-11 09:13:42 +08:00
|
|
|
/**
|
|
|
|
* scsi_cdl_enable - Enable or disable a SCSI device supports for Command
|
|
|
|
* Duration Limits
|
|
|
|
* @sdev: The target device
|
|
|
|
* @enable: the target state
|
|
|
|
*/
|
|
|
|
int scsi_cdl_enable(struct scsi_device *sdev, bool enable)
|
|
|
|
{
|
|
|
|
struct scsi_mode_data data;
|
|
|
|
struct scsi_sense_hdr sshdr;
|
|
|
|
struct scsi_vpd *vpd;
|
|
|
|
bool is_ata = false;
|
|
|
|
char buf[64];
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (!sdev->cdl_supported)
|
|
|
|
return -EOPNOTSUPP;
|
|
|
|
|
|
|
|
rcu_read_lock();
|
|
|
|
vpd = rcu_dereference(sdev->vpd_pg89);
|
|
|
|
if (vpd)
|
|
|
|
is_ata = true;
|
|
|
|
rcu_read_unlock();
|
|
|
|
|
|
|
|
/*
|
|
|
|
* For ATA devices, CDL needs to be enabled with a SET FEATURES command.
|
|
|
|
*/
|
|
|
|
if (is_ata) {
|
|
|
|
char *buf_data;
|
|
|
|
int len;
|
|
|
|
|
|
|
|
ret = scsi_mode_sense(sdev, 0x08, 0x0a, 0xf2, buf, sizeof(buf),
|
|
|
|
5 * HZ, 3, &data, NULL);
|
|
|
|
if (ret)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
/* Enable CDL using the ATA feature page */
|
|
|
|
len = min_t(size_t, sizeof(buf),
|
|
|
|
data.length - data.header_length -
|
|
|
|
data.block_descriptor_length);
|
|
|
|
buf_data = buf + data.header_length +
|
|
|
|
data.block_descriptor_length;
|
|
|
|
if (enable)
|
|
|
|
buf_data[4] = 0x02;
|
|
|
|
else
|
|
|
|
buf_data[4] = 0;
|
|
|
|
|
|
|
|
ret = scsi_mode_select(sdev, 1, 0, buf_data, len, 5 * HZ, 3,
|
|
|
|
&data, &sshdr);
|
|
|
|
if (ret) {
|
|
|
|
if (scsi_sense_valid(&sshdr))
|
|
|
|
scsi_print_sense_hdr(sdev,
|
|
|
|
dev_name(&sdev->sdev_gendev), &sshdr);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
sdev->cdl_enable = enable;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/**
|
2007-11-04 02:30:39 +08:00
|
|
|
* scsi_device_get - get an additional reference to a scsi_device
|
2005-04-17 06:20:36 +08:00
|
|
|
* @sdev: device to get a reference to
|
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Description: Gets a reference to the scsi_device and increments the use count
|
2005-04-17 06:20:36 +08:00
|
|
|
* of the underlying LLDD module. You must hold host_lock of the
|
|
|
|
* parent Scsi_Host or already have a reference when calling this.
|
2015-02-02 21:01:26 +08:00
|
|
|
*
|
|
|
|
* This will fail if a device is deleted or cancelled, or when the LLD module
|
|
|
|
* is in the process of being unloaded.
|
2005-04-17 06:20:36 +08:00
|
|
|
*/
|
|
|
|
int scsi_device_get(struct scsi_device *sdev)
|
|
|
|
{
|
2015-02-02 21:01:26 +08:00
|
|
|
if (sdev->sdev_state == SDEV_DEL || sdev->sdev_state == SDEV_CANCEL)
|
|
|
|
goto fail;
|
|
|
|
if (!try_module_get(sdev->host->hostt->module))
|
2022-10-15 08:24:17 +08:00
|
|
|
goto fail;
|
|
|
|
if (!get_device(&sdev->sdev_gendev))
|
|
|
|
goto fail_put_module;
|
2005-04-17 06:20:36 +08:00
|
|
|
return 0;
|
2015-02-02 21:01:26 +08:00
|
|
|
|
2022-10-15 08:24:17 +08:00
|
|
|
fail_put_module:
|
|
|
|
module_put(sdev->host->hostt->module);
|
2015-02-02 21:01:26 +08:00
|
|
|
fail:
|
|
|
|
return -ENXIO;
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(scsi_device_get);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* scsi_device_put - release a reference to a scsi_device
|
|
|
|
* @sdev: device to release a reference on.
|
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Description: Release a reference to the scsi_device and decrements the use
|
|
|
|
* count of the underlying LLDD module. The device is freed once the last
|
2005-04-17 06:20:36 +08:00
|
|
|
* user vanishes.
|
|
|
|
*/
|
|
|
|
void scsi_device_put(struct scsi_device *sdev)
|
|
|
|
{
|
2022-08-22 06:05:00 +08:00
|
|
|
struct module *mod = sdev->host->hostt->module;
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
put_device(&sdev->sdev_gendev);
|
2022-08-22 06:05:00 +08:00
|
|
|
module_put(mod);
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(scsi_device_put);
|
|
|
|
|
2007-11-04 02:30:39 +08:00
|
|
|
/* helper for shost_for_each_device, see that for documentation */
|
2005-04-17 06:20:36 +08:00
|
|
|
struct scsi_device *__scsi_iterate_devices(struct Scsi_Host *shost,
|
|
|
|
struct scsi_device *prev)
|
|
|
|
{
|
|
|
|
struct list_head *list = (prev ? &prev->siblings : &shost->__devices);
|
|
|
|
struct scsi_device *next = NULL;
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(shost->host_lock, flags);
|
|
|
|
while (list->next != &shost->__devices) {
|
|
|
|
next = list_entry(list->next, struct scsi_device, siblings);
|
|
|
|
/* skip devices that we can't get a reference to */
|
|
|
|
if (!scsi_device_get(next))
|
|
|
|
break;
|
|
|
|
next = NULL;
|
|
|
|
list = list->next;
|
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(shost->host_lock, flags);
|
|
|
|
|
|
|
|
if (prev)
|
|
|
|
scsi_device_put(prev);
|
|
|
|
return next;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(__scsi_iterate_devices);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* starget_for_each_device - helper to walk all devices of a target
|
|
|
|
* @starget: target whose devices we want to iterate over.
|
2007-11-04 02:30:39 +08:00
|
|
|
* @data: Opaque passed to each function call.
|
|
|
|
* @fn: Function to call on each device
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
2007-12-11 07:49:31 +08:00
|
|
|
* This traverses over each device of @starget. The devices have
|
2005-04-17 06:20:36 +08:00
|
|
|
* a reference that must be released by scsi_host_put when breaking
|
|
|
|
* out of the loop.
|
|
|
|
*/
|
2007-12-11 07:49:31 +08:00
|
|
|
void starget_for_each_device(struct scsi_target *starget, void *data,
|
2005-04-17 06:20:36 +08:00
|
|
|
void (*fn)(struct scsi_device *, void *))
|
|
|
|
{
|
|
|
|
struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);
|
|
|
|
struct scsi_device *sdev;
|
|
|
|
|
|
|
|
shost_for_each_device(sdev, shost) {
|
|
|
|
if ((sdev->channel == starget->channel) &&
|
|
|
|
(sdev->id == starget->id))
|
|
|
|
fn(sdev, data);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(starget_for_each_device);
|
|
|
|
|
2007-12-11 07:49:31 +08:00
|
|
|
/**
|
2008-02-04 07:06:36 +08:00
|
|
|
* __starget_for_each_device - helper to walk all devices of a target (UNLOCKED)
|
2007-12-11 07:49:31 +08:00
|
|
|
* @starget: target whose devices we want to iterate over.
|
2008-02-04 07:06:36 +08:00
|
|
|
* @data: parameter for callback @fn()
|
|
|
|
* @fn: callback function that is invoked for each device
|
2007-12-11 07:49:31 +08:00
|
|
|
*
|
|
|
|
* This traverses over each device of @starget. It does _not_
|
|
|
|
* take a reference on the scsi_device, so the whole loop must be
|
|
|
|
* protected by shost->host_lock.
|
|
|
|
*
|
|
|
|
* Note: The only reason why drivers would want to use this is because
|
|
|
|
* they need to access the device list in irq context. Otherwise you
|
|
|
|
* really want to use starget_for_each_device instead.
|
|
|
|
**/
|
|
|
|
void __starget_for_each_device(struct scsi_target *starget, void *data,
|
|
|
|
void (*fn)(struct scsi_device *, void *))
|
|
|
|
{
|
|
|
|
struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);
|
|
|
|
struct scsi_device *sdev;
|
|
|
|
|
|
|
|
__shost_for_each_device(sdev, shost) {
|
|
|
|
if ((sdev->channel == starget->channel) &&
|
|
|
|
(sdev->id == starget->id))
|
|
|
|
fn(sdev, data);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(__starget_for_each_device);
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/**
|
|
|
|
* __scsi_device_lookup_by_target - find a device given the target (UNLOCKED)
|
|
|
|
* @starget: SCSI target pointer
|
|
|
|
* @lun: SCSI Logical Unit Number
|
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Description: Looks up the scsi_device with the specified @lun for a given
|
|
|
|
* @starget. The returned scsi_device does not have an additional
|
2005-04-17 06:20:36 +08:00
|
|
|
* reference. You must hold the host's host_lock over this call and
|
2009-01-13 23:50:37 +08:00
|
|
|
* any access to the returned scsi_device. A scsi_device in state
|
|
|
|
* SDEV_DEL is skipped.
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
2007-11-16 07:42:30 +08:00
|
|
|
* Note: The only reason why drivers should use this is because
|
2007-11-04 02:30:39 +08:00
|
|
|
* they need to access the device list in irq context. Otherwise you
|
2005-04-17 06:20:36 +08:00
|
|
|
* really want to use scsi_device_lookup_by_target instead.
|
|
|
|
**/
|
|
|
|
struct scsi_device *__scsi_device_lookup_by_target(struct scsi_target *starget,
|
2014-06-25 21:27:36 +08:00
|
|
|
u64 lun)
|
2005-04-17 06:20:36 +08:00
|
|
|
{
|
|
|
|
struct scsi_device *sdev;
|
|
|
|
|
|
|
|
list_for_each_entry(sdev, &starget->devices, same_target_siblings) {
|
2009-01-13 23:50:37 +08:00
|
|
|
if (sdev->sdev_state == SDEV_DEL)
|
|
|
|
continue;
|
2005-04-17 06:20:36 +08:00
|
|
|
if (sdev->lun ==lun)
|
|
|
|
return sdev;
|
|
|
|
}
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(__scsi_device_lookup_by_target);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* scsi_device_lookup_by_target - find a device given the target
|
|
|
|
* @starget: SCSI target pointer
|
|
|
|
* @lun: SCSI Logical Unit Number
|
|
|
|
*
|
2009-04-28 02:54:22 +08:00
|
|
|
* Description: Looks up the scsi_device with the specified @lun for a given
|
|
|
|
* @starget. The returned scsi_device has an additional reference that
|
2007-11-04 02:30:39 +08:00
|
|
|
* needs to be released with scsi_device_put once you're done with it.
|
2005-04-17 06:20:36 +08:00
|
|
|
**/
|
|
|
|
struct scsi_device *scsi_device_lookup_by_target(struct scsi_target *starget,
|
2014-06-25 21:27:36 +08:00
|
|
|
u64 lun)
|
2005-04-17 06:20:36 +08:00
|
|
|
{
|
|
|
|
struct scsi_device *sdev;
|
|
|
|
struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(shost->host_lock, flags);
|
|
|
|
sdev = __scsi_device_lookup_by_target(starget, lun);
|
|
|
|
if (sdev && scsi_device_get(sdev))
|
|
|
|
sdev = NULL;
|
|
|
|
spin_unlock_irqrestore(shost->host_lock, flags);
|
|
|
|
|
|
|
|
return sdev;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(scsi_device_lookup_by_target);
|
|
|
|
|
|
|
|
/**
|
2007-11-04 02:30:39 +08:00
|
|
|
* __scsi_device_lookup - find a device given the host (UNLOCKED)
|
2005-04-17 06:20:36 +08:00
|
|
|
* @shost: SCSI host pointer
|
|
|
|
* @channel: SCSI channel (zero if only one channel)
|
2007-11-04 02:30:39 +08:00
|
|
|
* @id: SCSI target number (physical unit number)
|
2005-04-17 06:20:36 +08:00
|
|
|
* @lun: SCSI Logical Unit Number
|
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Description: Looks up the scsi_device with the specified @channel, @id, @lun
|
|
|
|
* for a given host. The returned scsi_device does not have an additional
|
|
|
|
* reference. You must hold the host's host_lock over this call and any access
|
|
|
|
* to the returned scsi_device.
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
|
|
|
* Note: The only reason why drivers would want to use this is because
|
2007-11-04 02:30:39 +08:00
|
|
|
* they need to access the device list in irq context. Otherwise you
|
2005-04-17 06:20:36 +08:00
|
|
|
* really want to use scsi_device_lookup instead.
|
|
|
|
**/
|
|
|
|
struct scsi_device *__scsi_device_lookup(struct Scsi_Host *shost,
|
2014-06-25 21:27:36 +08:00
|
|
|
uint channel, uint id, u64 lun)
|
2005-04-17 06:20:36 +08:00
|
|
|
{
|
|
|
|
struct scsi_device *sdev;
|
|
|
|
|
|
|
|
list_for_each_entry(sdev, &shost->__devices, siblings) {
|
2017-04-28 17:43:04 +08:00
|
|
|
if (sdev->sdev_state == SDEV_DEL)
|
|
|
|
continue;
|
2005-04-17 06:20:36 +08:00
|
|
|
if (sdev->channel == channel && sdev->id == id &&
|
|
|
|
sdev->lun ==lun)
|
|
|
|
return sdev;
|
|
|
|
}
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(__scsi_device_lookup);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* scsi_device_lookup - find a device given the host
|
|
|
|
* @shost: SCSI host pointer
|
|
|
|
* @channel: SCSI channel (zero if only one channel)
|
|
|
|
* @id: SCSI target number (physical unit number)
|
|
|
|
* @lun: SCSI Logical Unit Number
|
|
|
|
*
|
2007-11-04 02:30:39 +08:00
|
|
|
* Description: Looks up the scsi_device with the specified @channel, @id, @lun
|
|
|
|
* for a given host. The returned scsi_device has an additional reference that
|
|
|
|
* needs to be released with scsi_device_put once you're done with it.
|
2005-04-17 06:20:36 +08:00
|
|
|
**/
|
|
|
|
struct scsi_device *scsi_device_lookup(struct Scsi_Host *shost,
|
2014-06-25 21:27:36 +08:00
|
|
|
uint channel, uint id, u64 lun)
|
2005-04-17 06:20:36 +08:00
|
|
|
{
|
|
|
|
struct scsi_device *sdev;
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(shost->host_lock, flags);
|
|
|
|
sdev = __scsi_device_lookup(shost, channel, id, lun);
|
|
|
|
if (sdev && scsi_device_get(sdev))
|
|
|
|
sdev = NULL;
|
|
|
|
spin_unlock_irqrestore(shost->host_lock, flags);
|
|
|
|
|
|
|
|
return sdev;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(scsi_device_lookup);
|
|
|
|
|
|
|
|
MODULE_DESCRIPTION("SCSI core");
|
|
|
|
MODULE_LICENSE("GPL");
|
|
|
|
|
|
|
|
module_param(scsi_logging_level, int, S_IRUGO|S_IWUSR);
|
|
|
|
MODULE_PARM_DESC(scsi_logging_level, "a bit mask of logging levels");
|
|
|
|
|
|
|
|
static int __init init_scsi(void)
|
|
|
|
{
|
2006-10-01 02:31:11 +08:00
|
|
|
int error;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
error = scsi_init_procfs();
|
|
|
|
if (error)
|
|
|
|
goto cleanup_queue;
|
|
|
|
error = scsi_init_devinfo();
|
|
|
|
if (error)
|
|
|
|
goto cleanup_procfs;
|
|
|
|
error = scsi_init_hosts();
|
|
|
|
if (error)
|
|
|
|
goto cleanup_devlist;
|
|
|
|
error = scsi_init_sysctl();
|
|
|
|
if (error)
|
|
|
|
goto cleanup_hosts;
|
|
|
|
error = scsi_sysfs_register();
|
|
|
|
if (error)
|
|
|
|
goto cleanup_sysctl;
|
|
|
|
|
[SCSI] SCSI and FC Transport: add netlink support for posting of transport events
This patch formally adds support for the posting of FC events via netlink.
It is a followup to the original RFC at:
http://marc.theaimsgroup.com/?l=linux-scsi&m=114530667923464&w=2
and the initial posting at:
http://marc.theaimsgroup.com/?l=linux-scsi&m=115507374832500&w=2
The patch has been updated to optimize the send path, per the discussions
in the initial posting.
Per discussions at the Storage Summit and at OLS, we are to use netlink for
async events from transports. Also per discussions, to avoid a netlink
protocol per transport, I've create a single NETLINK_SCSITRANSPORT protocol,
which can then be used by all transports.
This patch:
- Creates new files scsi_netlink.c and scsi_netlink.h, which contains the
single and shared definitions for the SCSI Transport. It is tied into the
base SCSI subsystem intialization.
Contains a single interface routine, scsi_send_transport_event(), for a
transport to send an event (via multicast to a protocol specific group).
- Creates a new scsi_netlink_fc.h file, which contains the FC netlink event
messages
- Adds 3 new routines to the fc transport:
fc_get_event_number() - to get a FC event #
fc_host_post_event() - to send a simple FC event (32 bits of data)
fc_host_post_vendor_event() - to send a Vendor unique event, with
arbitrary amounts of data.
Note: the separation of event number allows for a LLD to send a standard
event, followed by vendor-specific data for the event.
Note: This patch assumes 2 prior fc transport patches have been installed:
http://marc.theaimsgroup.com/?l=linux-scsi&m=115555807316329&w=2
http://marc.theaimsgroup.com/?l=linux-scsi&m=115581614930261&w=2
Sorry - next time I'll do something like making these individual
patches of the same posting when I know they'll be posted closely
together.
Signed-off-by: James Smart <James.Smart@emulex.com>
Tidy up configuration not to make SCSI always select NET
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
2006-08-19 05:30:09 +08:00
|
|
|
scsi_netlink_init();
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
printk(KERN_NOTICE "SCSI subsystem initialized\n");
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
cleanup_sysctl:
|
|
|
|
scsi_exit_sysctl();
|
|
|
|
cleanup_hosts:
|
|
|
|
scsi_exit_hosts();
|
|
|
|
cleanup_devlist:
|
|
|
|
scsi_exit_devinfo();
|
|
|
|
cleanup_procfs:
|
|
|
|
scsi_exit_procfs();
|
|
|
|
cleanup_queue:
|
|
|
|
scsi_exit_queue();
|
|
|
|
printk(KERN_ERR "SCSI subsystem failed to initialize, error = %d\n",
|
|
|
|
-error);
|
|
|
|
return error;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void __exit exit_scsi(void)
|
|
|
|
{
|
[SCSI] SCSI and FC Transport: add netlink support for posting of transport events
This patch formally adds support for the posting of FC events via netlink.
It is a followup to the original RFC at:
http://marc.theaimsgroup.com/?l=linux-scsi&m=114530667923464&w=2
and the initial posting at:
http://marc.theaimsgroup.com/?l=linux-scsi&m=115507374832500&w=2
The patch has been updated to optimize the send path, per the discussions
in the initial posting.
Per discussions at the Storage Summit and at OLS, we are to use netlink for
async events from transports. Also per discussions, to avoid a netlink
protocol per transport, I've create a single NETLINK_SCSITRANSPORT protocol,
which can then be used by all transports.
This patch:
- Creates new files scsi_netlink.c and scsi_netlink.h, which contains the
single and shared definitions for the SCSI Transport. It is tied into the
base SCSI subsystem intialization.
Contains a single interface routine, scsi_send_transport_event(), for a
transport to send an event (via multicast to a protocol specific group).
- Creates a new scsi_netlink_fc.h file, which contains the FC netlink event
messages
- Adds 3 new routines to the fc transport:
fc_get_event_number() - to get a FC event #
fc_host_post_event() - to send a simple FC event (32 bits of data)
fc_host_post_vendor_event() - to send a Vendor unique event, with
arbitrary amounts of data.
Note: the separation of event number allows for a LLD to send a standard
event, followed by vendor-specific data for the event.
Note: This patch assumes 2 prior fc transport patches have been installed:
http://marc.theaimsgroup.com/?l=linux-scsi&m=115555807316329&w=2
http://marc.theaimsgroup.com/?l=linux-scsi&m=115581614930261&w=2
Sorry - next time I'll do something like making these individual
patches of the same posting when I know they'll be posted closely
together.
Signed-off-by: James Smart <James.Smart@emulex.com>
Tidy up configuration not to make SCSI always select NET
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
2006-08-19 05:30:09 +08:00
|
|
|
scsi_netlink_exit();
|
2005-04-17 06:20:36 +08:00
|
|
|
scsi_sysfs_unregister();
|
|
|
|
scsi_exit_sysctl();
|
|
|
|
scsi_exit_hosts();
|
|
|
|
scsi_exit_devinfo();
|
|
|
|
scsi_exit_procfs();
|
|
|
|
scsi_exit_queue();
|
|
|
|
}
|
|
|
|
|
|
|
|
subsys_initcall(init_scsi);
|
|
|
|
module_exit(exit_scsi);
|