- Make esp_bootup_reset() global again, since the Amiga Oktagon SCSI driver
    needs it, and move its prototype from oktagon_esp.c to NCR53C9x.h
  - Make esp_cmd() static in the debug case. It's already a local macro in the
    non-debug case.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

   - expand sense data handling to descriptor format
   - make module parameters visible in
       /sys/modules/sg/parameters
   - add "readable" SCSI commands: READ(16), REPORT LUNS,
     SERVICE_ACTION_IN, RECEIVE_DIAGNOSTIC, READ_LONG
     and MAINTENANCE_IN_CMD to list
Signed-off-by: Douglas Gilbert <dougg@torque.net>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

This converts the three transport classes (SPI, FC and iSCSI) over to
the generic transport class code.

It also converts the internals of the SCSI mid-layer to use generic
transport class trigger points and pulls out some of the duplicated code.
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

Transport classes are a mechanism for providing transport specific
services to drivers that the more generic command processing layers
don't care about.  A good example is the SCSI mid-layer not caring about
parallel transfer characteristics or providing services for domain
validation.  Transport classes usually provide a transport specific API
at one end and a class interface at the other (for the user to
interrogate and set parameters).

Originally, transport classes were SCSI specific.  However, this code is
generic to the device model.  As long as you have a generic device
representing a storage interface (or device) then you can attach a
transport class to it.  The new code also allows an arbitrary number of
transport classes to be attached to a device, unlike SCSI which only
allowed one.  This is going to be important for things like SATA and SAS
which share the PHY layer (and hence should be capable of sharing a PHY
transport class).

The generic transport class is designed to operate identically to the
current SCSI transport classes, except that it uses generic devices
rather than SCSI devices.
 
We have five events:
 
 setup
 add
 -----
 configure
 -----
 remove
 destroy

With callbacks for setup configure and remove.

There's also an anonymous transport class which can only respond to 
configure events (and which has no attributes).
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

Attribute containers allows a single device to belong to an arbitrary
number of classes, each with an arbitrary number of attributes.

This will be used as the basis for a generic transport class
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

kref_put could free the cd structure.  We need a copy
of cd->device to do a scsi_device_put after the
kref_put.
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

This patch:

http://linux-scsi.bkbits.net:8080/scsi-for-linus-2.6/cset@1.2034.95.5?nav=index.html|src/|src/drivers|src/drivers/scsi|related/drivers/scsi/sd.c

is causing almost as much trouble as it fixed.  If kref_put() drops the
last reference to the scsi_disk (this happens when the device file is
closed after the device has been hot-unplugged) then the call to
scsi_device_put() will take its argument from an area of memory that has
been deallocated.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

The dsense switch in the scsi_debug driver selects
whether fixed (default) or descriptor format sense
data is returned when an error/warning occurs. Due
to an oversight dsense was not sysfs visible.
Signed-off-by: Douglas Gilbert <dougg@torque.net>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

There was a patch to *remove* that line completely issued about a month
ago. It is a case of a second schedule_timeout left over from an editing
mistake made long ago in a distant galaxy.
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

From: 	James.Smart@Emulex.Com

This patch adds 5 more FC transport host attributes in support of HBAAPI. 
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

From: 	James.Smart@Emulex.Com

This patch deprecates the use of device_for_each_child() with stargets.
The reasoning behind this is due to issues regarding:
      Semaphores that device_for_each_child() takes
      Implicit assumptions that each child is an sdev device.

The patch adds a new helper function, starget_for_each_device(), and
replaces all previous uses of device_for_each_child().
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

From: Jesse Barnes <jbarnes@engr.sgi.com>

There are a few spots in qla1280.c that don't need a full PCI write flush
to the device, but rather a simple write ordering guarantee.  This patch
changes some of the PIO reads that cause write flushes into mmiowb calls
instead, which is a lighter weight way of ensuring ordering.
Signed-off-by: Jeremy Higdon <jeremy@sgi.com>
Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

From: Adrian Bunk <bunk@stusta.de>

The patch below kills kernel 2.2 #ifdef's from the SCSI aic7xxx driver.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>

This is really part of the earlier changeset from David to add the
new machine vector to support certain limited range DMA cards on
zx1.  I just forgot to run "bk new" before the commit, so the newly
added files weren't checked into BK.
Signed-off-by: David Mosberger-Tang <davidm@hpl.hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>

In ChangeSet 1.2370, 2005/01/11 17:41:32-08:00, tglx@linutronix.de wrote:
>
>         [PATCH] ppc: remove duplicate define
>        
>         The MMCR0_PMXE is already defined in reg.h...

Er, no it's not. But perhaps it should be...

Ingo presumably didn't notice that ppc64 already had a functional
_raw_read_trylock when he added the #define to use the generic
version.  This just removes the #define so we use the ppc64-specific
version again.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Currently we only print the default io scheduler if the kernel chooses,
not if the user/bootloader has specified one. This patch saves the extra
line in dmesg but always notified of the default choice by appending
(default) to that line:

	..
	io scheduler noop registered
	io scheduler anticipatory registered
	io scheduler deadline registered
	io scheduler cfq registered (default)
	..

Patch originally from Srihari Vijayaraghavan, modified by me.
Signed-off-by: Jens Axboe <axboe@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Signed-off-by: Tony Luck <tony.luck@intel.com>

The accounting can go bad in the requeue hook, it must check the
accounted flag to make sure it was previously considered in the driver.
Signed-off-by: Jens Axboe <axboe@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Signed-off-by: Keith Owens <kaos@sgi.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

This apparently explains some weird IO failures reported in last two months.
Only non-bwx (including generic) kernels were affected.
Acked-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

This enables it only for debug kernels, and also makes sure
that if some external module is still broken, we don't leave
the mmap-sem locked after warning about it.

It seems to be general consensus that its safer to require all do_brk() callers
to grab mmap_sem, and have do_brk to warn otherwise. This is what the following
patch does.

Similar version has been changed to in v2.4.
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

We had all the locking right, but we didn't check whether one of the
threads now no longer needed to expand, so we could incorrectly _shrink_
the stack in the other thread instead (not only causing segfaults, but
since we didn't do a proper unmap, we'd possibly leak pages too).

So re-check the need for expand after getting the lock.

Noticed by Paul Starzetz.

Fix a long standing bug: numa=off only worked as last argument on
the command line.
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Fix K8 node discovery after nodemask changes.
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Fix fallout from the recent nodemask_t changes. The node ids assigned
in the SRAT parser were off by one.

I added a new first_unset_node() function to nodemask.h to allocate
IDs sanely.
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

drivers/net/3c515.c: In function `__check_rx_copybreak':
drivers/net/3c515.c:406: warning: return discards qualifiers from pointer target type
drivers/net/3c515.c: At top level:
drivers/net/3c515.c:406: warning: initialization discards qualifiers from pointer target type
Signed-off-by: Andrew Morton <akpm@osdl.org>

Signed-off-by: Andrew Morton <akpm@osdl.org>

drivers/net/eepro.c:1799: initializer element is not constant
drivers/net/eepro.c:1799: (near initialization for `__param_arr_io.num')
drivers/net/eepro.c:1800: initializer element is not constant
drivers/net/eepro.c:1800: (near initialization for `__param_arr_irq.num')
drivers/net/eepro.c:1801: initializer element is not constant
drivers/net/eepro.c:1801: (near initialization for `__param_arr_mem.num')
Signed-off-by: Andrew Morton <akpm@osdl.org>

into pobox.com:/garz/repo/net-drivers-2.6

I found bugs on error handlings in the functions arround the ext3 file
system, which cause inadequate completions of synchronous write I/O
operations when disk I/O failures occur.  Both 2.4 and 2.6 have this
problem.

	I carried out following experiment:

1.  Mount a ext3 file system on a SCSI disk with ordered mode.
2.  Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT flag.
3.  Write 512 bytes data to the file by calling write() every 5 seconds, and
     examine return values from the syscall.
     from write().
4.  Disconnect the SCSI cable,  and examine messages from the kernel.

After the SCSI cable is disconnected, write() must fail.  But the result
was different: write() succeeded for a while even though messages of the
kernel notified SCSI I/O error.

By applying following modifications, the above problem was solved.
Signed-off-by: Hisashi Hifumi <hifumi.hisashi@lab.ntt.co.jp>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>