Kernel patches

2004-06-14 kernel 2.4.21 bug fix patch 14 ("June 2003")

If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.

linux-2.4.21-s390-14-june2003.tar.gz / MD5 ... accumulated patch, recommended (2004-06-14)

linux-2.4.21-s390-14-june2003-patches.tar.gz / MD5 ... per-problem-patches, recommended (2004-06-14)

These patches contain the following linux kernel bug fixes:

Description:
cio: Deferred cc=3 on BASIC SENSE leads to data corruption.
Symptom:
Data corruption after heavy I/O workload while ESS is doing failover.
Problem:
BASIC SENSE after a unit check returns with deferred cc=3. The device driver is called with the device status for the BASIC SENSE which it should not see.
Solution:
If a deferred cc=3 happens after a BASIC SENSE, call the device driver with the device status for the preceding unit check and reset the w4sense flag.
Problem-ID:
9055
Description:
network: multicast joins and drops not noticed by drivers.
Symptom:
Multicast traffic is not received by applications.
Problem:
Driver did not notice stack using multicast addresses.
Solution:
Use notifier_call_chain to notify drivers. A device driver can use register_multicast_notifier to be informed about multicast changes on the interfaces.
Problem-ID:
9211
Description:
zfcp: performance patch 1/6.
Symptom:
Small performance decrease due to zfcp_lock debug feature.
Problem:
Excessive collection of debug data.
Solution:
Removal of zfcp_lock debug feature.
Problem-ID:
9191
Description:
zfcp: performance patch 2/6.
Symptom:
Small performance decrease due to zfcp_req debug feature.
Problem:
Excessive debug data collection.
Solution:
Adjustment of verbosity of zfcp_req debug feature (turned off unless changed by user).
Problem-ID:
9192
Description:
zfcp: performance patch 3/6.
Symptom:
Small performance decrease due to lockmeter applied to outbound queue.
Problem:
Excessive scrutiny as to lock contention.
Solution:
Removal of lockmeter.
Problem-ID:
9193
Description:
zfcp: performance patch 4/6.
Symptom:
Small performance decrease due to paranoia checks.
Problem:
Excessive checking of I/O request.
Solution:
Reduction of paranoia checks.
Problem-ID:
9194
Description:
zfcp: performance patch 5/6.
Symptom:
Small performance decrease due to logging.
Problem:
Excessive use of printk logging.
Solution:
Adjustment of maximum logging level to DEBUG (=2) to make the preprocessor remove certain messages and the corresponding logging level checks.
Problem-ID:
9195
Description:
zfcp: performance patch 6/6.
Symptom:
Small performance decrease due to I/O statistics.
Problem:
Excessive and expensive statistics.
Solution:
Reduction of I/O statistics by two thirds. Statistics per adapter instead of global statistics to minimize lock contention. Optimization of statistics update operation. User interface for toggling statistics on/off (turned off unless changed by user).
Problem-ID:
9196
Description:
zfcp: scsi devices set offline.
Symptom:
The SCSI stack set devices offline and SCSI commands were failed with host_byte 0xf. In an LVM multipathed environment this failure could have caused the loss of paths to SCSI devices.
Problem:
The scsi_cmnd->result member was not zeroed in some cases. Since results are or-ed into this member, this resulted in incorrect values in some cases.
Solution:
Always zero scsi_cmnd->result for every scsi_cmnd passed to zfcp.
Problem-ID:
8674
Description:
zfcp: unable to recover 'local link down' at init time.
Symptom:
FCP subchannel remains shut down (marked unused in /proc/subchannels) when trying to start it up (by adding an FCP address mapping for that adapter, or by triggering "reset erp", or by config off/on, or by replugging the fibre) while the local link is unplugged.
Problem:
zfcp driver did not take the FSF_EXCHANGE_CONFIG_DATA_INCOMPLETE status into account, but shut an adapter down on that condition.
Solution:
The zfcp driver must not shut the adapter down in order to be able to receive a 'local link up' indication once the fibre has been replugged.
Problem-ID:
7739

Everybody should apply this patch.

To create the complete linux kernel sources, the following patches need to be applied in sequence:

linux-2.4.21.tar.gz (see www.kernel.org)
+ linux-2.4.21-s390-june2003.diff (IBM)
+ linux-2.4.21-s390-01-june2003.diff (IBM)
+ linux-2.4.21-s390-02-june2003.diff (IBM)
+ linux-2.4.21-s390-03-june2003.diff (IBM)
+ linux-2.4.21-s390-04-june2003.diff (IBM)
+ linux-2.4.21-s390-05-june2003.diff (IBM)
+ linux-2.4.21-s390-06-june2003.diff (IBM)
+ linux-2.4.21-s390-07-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-09-june2003.diff (IBM)
+ linux-2.4.21-s390-10-june2003.diff (IBM)
+ xip2fs1 (see linuxvm.org/patches/index.html)
+ xip2fs2 (see linuxvm.org/patches/index.html)
+ linux-2.4.21-s390-11-june2003.diff (IBM)
+ linux-2.4.21-s390-12-june2003.diff (IBM)
+ linux-2.4.21-s390-13-june2003.diff (IBM)
+ linux-2.4.21-s390-14-june2003.diff (IBM)

Note: If On-demand timer is required, apply as last patch:
+ linux-2.4.21-s390-timer-03-june2003.diff (IBM)

Contact the IBM team

If you want to contact the Linux on System z IBM team refer to the Contact the Linux on System z IBM team page.