Patrick pointed out that I could get into a ABBA issue with holding
list_lock while calling scsi_eh_scmd_add which takes host_lock.
A call to scsi_prep_fn already holds the queue_lock and then makes a
call to scsi_get_command which takes list_lock.

-andmike
--
Michael Anderson
andmike@us.ibm.com

=====
name:		00_scsi_set_device_offline.diff
version:	2003-02-26.15:18:19-0800
against:	scsi-misc-2.5

 scsi.c |   15 +++++++++------
 1 files changed, 9 insertions(+), 6 deletions(-)

=====

Against 2.5.63, untested

regards
john

On Wed, Feb 26, 2003 at 08:20:05PM +0100, Christoph Hellwig wrote:
> This patch updates nsp_cs to use scsi_add_host / scsi_remove_host when
> compiledfor Linux 2.5 which allows to get rid of the scsi host list
> walks and is a preparation for allowing to support multiple cards of
> this type.

Sorry, I sent you the wrong paetch, here's the right one:

Against 2.5.63, untested

regards
john

Against 2.5.63, untested

regards
john

Untested, against 2.5.63

regards
john

Untested, 2.5.63

I remember having this submitted a while ago, but here's the code
again, this time with the untested aic79xx bits.

Not tested, against 2.5.63

regards
john

This patch makes sure that there is a "0x" in front of all hex numbers and
makes all outputs use a single style (all %x instead of mixed %x and %X).

Eike

into raven.il.steeleye.com:/home/jejb/BK/scsi-misc-2.5

Same bug as other sym driver.

Spelling fixes! Woo! I gotta get me some of that.

First hunk is unexplained.
Second hunk had the 2.4 changeset comment 'fix warnings'

This made it into 2.4, and aparently fixes
a problem with some tape devices.

>From 2.4

Hello, I work on the Sun StorEdge[tm] arrays for Sun Microsystems, Inc.
As part of my testing of Linux, the attached changes are needed to enable
Sparse LUN support for Sun StorEdge[tm] arrays.

James' scsi tree already contains an big update to wd33c93 that will make
integrating pc980155 a lot easier - it will hopefully appear in 2.5.63.

I've done some more work on the bios parameter stuff, this is the patch
I came up with, James can you merge it into the linux-scsi tree?  It just
adds a new file for pc98-style bios geometry to the scsi core.

Data direction is now provided by the SCSI mid-layer

This converts /proc/io{mem,ports} to the seq_file interface
(single_open).

This patch fixes the incomplete data return problem of /proc/ide/triflex.
When the number of consecutive read bytes are smaller than the total
data in triflex_get_info(), the second read() returns 0.

Fixes for the 31 bit compatability layer:
 * add compat function for jiffies_to_timeval
 * convert parameters of clone system call
 * incorporate changes from setup_arg_pages to setup_arg_pages32
 * incorporate changes from do_execve to do_execve32
 * take care of nanosecond field in struct timespec
 * remove functions of old module system calls
 * add TIF_31BIT thread flag and replace S390_FLAG_31BIT with it
 * add arch_get_unmapped_area
 * add wrapper for sys_set_tid_address

Add missing/fix existing s390 relocations in the kernel module loader.

trivial s390 fixes/typos.

updates for s390 scsi support

- remove bogus header file
- add a definition for free_dma() to make scsi.c work

updates for unified netdev config

- remove duplicate questions from drivers/s390/Kconfig
- some trivial fixes to make the s390 specific options work
- new default configurations

clean up the IUCV driver

updates for compiling with gcc-3.3pre

- add -finline-limit=10000 to make it build
- drop .eh_frame elf section from vmlinux
- fix common warnings inn asm headers
- make dasd compile
- Don't warn about signed/unsigned comparisions
- fix inline syscall macros

update extable support in s390 and s390x

this makes use of the unified extable code.
for 31 bit s390, this is slightly more complicated
than the other architectures, but as long as
no one outside /arch uses search_exception_tables,
everything should work nicely

minor changes to s390 documentation

updates for s390 dasd driver

Some problems have been found in the dasd error handling code, they
are fixed by the update to dasd_3990_erp.c.

Dasd is one of only two remaining drivers that use the null
elevator instead of iosched. Appearantly, the null elevator
has some bitrot and can result in random data loss. For now,
we just don't use it.