From: Douglas Gilbert <dougg@torque.net>
To: linux-scsi@vger.kernel.org
Subject: [PATCH] scsi_debug version 1.61
Date: Wed, 17 Jul 2002 09:37:57 -0400 [thread overview]
Message-ID: <3D357335.468989F5@torque.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
I have reworked the scsi_debug driver mainly to add
kernel timers to simulate delayed responses. This is
more realistic that returning immediately and allows
commands to become queued. The length of the delay is
controlled by a new boot line/module option: "scsi_debug_delay".
Other changes:
- support REPORT LUNS
- support more MODE SENSE pages
- [following Doug Ledford's suggestion] do autsense
(i.e. set Scsi_Cmnd::sense_buffer array appropriately
when a status of CHECK CONDITION is set)
- minor driverfs support
- start adding error injection logic, see
"scsi_debug_every_nth"
At the moment the only driverfs support is creating the
directory: /driverfs/bus/scsi/drivers/scsi_debug
Patrick Mochel sent a patch to lkml that would have allowed
driver parameters to be placed in that directory. That patch
didn't make it into lk 2.5.26 .
I'm interested in "clean" ways to inject errors. This would
allow, for example, people to observe (and fix) what happens
when QUEUE_FULL is returned for the first queued command.
The attachment is a patch against lk 2.5.26 . The full driver
and some documentation can be found at
http://www.torque.net/sg/sdebug.html
I hope to backport this version to lk 2.4 (where it will become
scsi_debug version 0.61) shortly.
Doug Gilbert
[-- Attachment #2: scsi_debug_161.diff.gz --]
[-- Type: application/x-gzip, Size: 11316 bytes --]
next reply other threads:[~2002-07-17 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 13:37 Douglas Gilbert [this message]
2002-07-19 16:02 ` [PATCH] scsi_debug version 1.61 Douglas Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D357335.468989F5@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox