linux.git/drivers/s390, branch v2.6.23

Merge master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6

2007-09-11T14:46:09+00:00

* master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6:
  [SCSI] libiscsi: sync up iscsi and scsi eh's access to the connection
  [SCSI] libiscsi: fix null ptr regression when aborting a command with data to transfer
  [SCSI] qla2xxx: Update version number to 8.02.00-k3.
  [SCSI] qla2xxx: Correct mailbox register dump for FWI2 capable ISPs.
  [SCSI] qla2xxx: Correct 8GB iIDMA support.
  [SCSI] qla2xxx: Correct management-server login-state synchronization issue.
  [SCSI] qla2xxx: Don't modify parity bits during ISP25XX restart.
  [SCSI] qla2xxx: Allocate enough space for the full PCI descriptor.
  [SCSI] zfcp: fix the data buffer accessor patch
  [SCSI] zfcp: allocate gid_pn_data objects from gid_pn_cache
  [SCSI] zfcp: fix memory leak

qeth: Drop ARP packages on HiperSockets interface with NOARP attribute.

2007-08-31T10:52:58+00:00

A network interface can get ARP packets even when the interface has
NOARP specified. In a HiperSockets environment this disturbs receiving
systems when packets are sent on the multicast queue. (E.g. TCP/IP on
z/VM issues messages reporting invalid data on the HiperSockets
interface.)
Qeth will no longer send ARP packets on HiperSockets interface when
interface has the NOARP attribute.

Signed-off-by: Klaus D. Wacker 
Signed-off-by: Ursula Braun 
Signed-off-by: Jeff Garzik

qeth: provide specific message for OSA-adapters exclusively used

2007-08-31T10:52:58+00:00

Exclusive usage of OSA-cards has been introduced. Even though Linux
does not make use of it, qeth should be prepared to receive a bad RC
for some initialization steps. A meaningful message is now given,
if an OSA-device is set online, even though the OSA-adapter is already
exclusively used by another host.

Signed-off-by: Ursula Braun 
Signed-off-by: Jeff Garzik

qeth: crash during reboot after failing online setting

2007-08-31T10:52:58+00:00

Online setting of a qeth device may fail for instance because of:
- out-of-memory condition when allocating qdio queues
- IDX ACTIVATE problem
- ...
Such a device is still returned in a driver_for_each_device loop
processed in qeth_reboot_event(), which calls
qeth_clear_qdio_buffers(). Make sure qeth_clear_output_buffer() is
called only, if the qdio queues have been successfully allocated
during initialization of a qeth device.

Signed-off-by: Ursula Braun 
Signed-off-by: Jeff Garzik

qeth: Announce tx checksumming for qeth devices in TSO/EDDP mode

2007-08-31T10:52:58+00:00

TSO requires tx checksumming. For non GSO frames in TSO/EDDP mode we
have to manually calculate the checksum.

Signed-off-by: Frank Blaschka 
Signed-off-by: Ursula Braun 
Signed-off-by: Jeff Garzik

qeth: dont return the return values of void functions.

2007-08-31T10:52:58+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Ursula Braun 
Signed-off-by: Jeff Garzik

qeth: enforce a rate limit for inbound scatter gather messages

2007-08-31T10:52:57+00:00

under memory pressure scatter gather mode switching messages must be
rate limited.

Signed-off-by: Frank Blaschka 
Signed-off-by: Ursula Braun 
Signed-off-by: Jeff Garzik

qeth: ungrouping a device must not be interruptible

2007-08-31T10:52:57+00:00

Problem:
A recovery thread must not be active when device is removed.
In qeth_remove_device() an interruptible wait operation is used
to wait until a qeth recovery thread is finished. If a user really
interrupts the ungroup operation of a qeth device while a recovery
is running, cio and qeth are out of sync (device already removed
from cio, but kept in qeth). A following module unload of qeth
results in a kernel OOPS here.

Solution:
Do not allow interruption of ungroup operation to guarantee
finishing of a potentially running qeth recovery thread.

Signed-off-by: Ursula Braun 
Signed-off-by: Jeff Garzik

[S390] vmur: fix reference counting for vmur device structure

2007-08-22T11:51:48+00:00

When a vmur device is removed due to a detach of the device, currently the
ur device structure is freed. Unfortunately it can happen, that there is
still a user of the device structure, when the character device is open
during the detach process. To fix this, reference counting for the vmur
structure is introduced.
In addition to that, the online, offline, probe and remove functions are
serialized now using a global mutex.

Signed-off-by: Michael Holzheu 
Signed-off-by: Martin Schwidefsky 
Signed-off-by: Heiko Carstens

[S390] vmur: fix diag14 exceptions with addresses > 2GB.

2007-08-22T11:51:47+00:00

There are several s390 diagnose calls, which must be executed below the
2GB memory boundary. In order to enforce this, those diagnoses must be
compiled into the kernel. Currently diag 14 can be called within the
vmur kernel module from addresses above 2GB. This leads to specification
exceptions. This patch moves diag10, diag14 and diag210 into the new
diag.c file.

Signed-off-by: Michael Holzheu 
Signed-off-by: Martin Schwidefsky 
Signed-off-by: Heiko Carstens